From: Sam Vilain <sam@vilain.net>
To: git@vger.kernel.org
Cc: gittorrent@lists.utsl.gen.nz
Subject: Update to "Peer Wire Guidelines" on GitTorrent RFC
Date: Mon, 28 Jul 2008 12:30:52 +1200 [thread overview]
Message-ID: <488D133C.1090704@vilain.net> (raw)
During the development of GitTorrent, I was being asked questions that
led me to realise that there wasn't a very good overall view of how the
various proposed GitTorrent messages fit together to make fetches work.
So, I've written a whole lot more on this with a few paragraphs which I
hope will pull it all together. If you found the RFC previously
indigestable, try reading:
http://gittorrent.utsl.gen.nz/rfc.html#peer-wire-guidelines
If there are parts which still aren't clear, please ask questions and I
will aim to write more clarification to the specification.
Cheers!
Sam.
reply other threads:[~2008-07-28 0:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=488D133C.1090704@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=gittorrent@lists.utsl.gen.nz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.