From: ori@eigenstate.org
To: lucio.dere@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] Getting git9 -- moved to github.
Date: Sun, 2 Feb 2020 16:55:15 -0800 [thread overview]
Message-ID: <20525BCC22B596CE9E7667B23350CCCB@eigenstate.org> (raw)
In-Reply-To: <CAJQ9t7itEjbTPskTVMkpc7QeUAatrc8H04MQy9gVygj5FDye4Q@mail.gmail.com>
> I made some changes to git9/proto.c that seem to handle
>
> git/fetch git+ssh://git@git.ff.co.za:23456/waspa/console.git
>
> successfully. What is the procedure to submit such (small) changes for
> inclusion?
Put the code in an email. Ideally to this list so we can get more
eyeballs looking over it. Put the patch into the body of the email
instead of attaching, for easier review and commenting.
The output of 'git/diff' should be sufficient for applying with
ape/patch.
Also, if you're changing the URL parsing, take a look at this:
https://raw.githubusercontent.com/git/git/master/Documentation/urls.txt
If we make changes, it would be worth fixing compatibility so that you
can just paste in any git url.
(Note that we don't yet have local repositories: That would require a
git/serve command)
next prev parent reply other threads:[~2020-02-03 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 17:03 ori
2020-01-27 21:23 ` [9fans] " Sergey Zhilkin
2020-02-02 9:58 ` Lucio De Re
2020-02-02 10:35 ` kvik
2020-02-02 14:39 ` Lucio De Re
2020-02-02 22:47 ` hiro
2020-02-02 23:28 ` cinap_lenrek
2020-02-03 0:55 ` ori [this message]
2020-02-03 0:57 ` ori
2020-02-03 4:07 ` Lucio De Re
2020-02-03 4:11 ` ori
2020-02-03 7:39 ` Lucio De Re
2020-02-03 10:01 ` hiro
2020-02-03 11:10 ` Lucio De Re
2020-02-03 13:54 ` hiro
2020-02-03 14:40 ` Lucio De Re
2020-02-03 16:14 ` ori
2020-02-04 4:07 ` Lucio De Re
2020-06-20 15:58 ` Lucio De Re
2020-02-03 20:42 ` cinap_lenrek
2020-02-04 4:03 ` Lucio De Re
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20525BCC22B596CE9E7667B23350CCCB@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
--cc=lucio.dere@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).