From: Junio C Hamano <firstname.lastname@example.org> To: Jonathan Tan <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [WIP RFC 1/5] Documentation: order protocol v2 sections Date: Sun, 09 Dec 2018 09:15:35 +0900 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Jonathan Tan <email@example.com> writes: >> > The git command line expects Git servers to follow a specific order of >> >> "Command line"? It sounds like you are talking about the order of >> command line arguments and options, but apparently that is not what >> you are doing. Is it "The git over-the-wire protocol"? > > I meant to say the current Git implementation, as opposed to what is > written in the specification. I'll replace it with "The current C Git > implementation". Yeah, that would avoid confusing future readers; sounds good. >> Earlier, we said that shallow-info is not given when packfile is not >> there. That is captured in the updated EBNF above. We don't have a >> corresponding removal of a bullet point for wanted-refs section below >> but probably that is because the original did not have corresponding >> bullet point to begin with. > > That's because the corresponding bullet point had other information. > Quoted in full below: > >> * This section is only included if the client has requested a >> ref using a 'want-ref' line and if a packfile section is also >> included in the response. > > I could reword it to "If a packfile section is included in the response, > this section is only included if the client has requested a ref using a > 'want-ref' line", but I don't think that is significantly clearer. I don't either. I didn't mean to suggest to change anything in this part. I was just giving an observation---two parallel things do not get updates in tandem, and that is because they were not described the same way to begin with, which was a good enough explanation.
next prev parent reply index Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-03 23:37 [WIP RFC 0/5] Design for offloading part of packfile response to CDN Jonathan Tan 2018-12-03 23:37 ` [WIP RFC 1/5] Documentation: order protocol v2 sections Jonathan Tan 2018-12-05 4:10 ` Junio C Hamano 2018-12-06 22:54 ` Jonathan Tan 2018-12-09 0:15 ` Junio C Hamano [this message] 2018-12-03 23:37 ` [WIP RFC 2/5] Documentation: add Packfile URIs design doc Jonathan Tan 2018-12-04 0:21 ` Stefan Beller 2018-12-04 1:54 ` brian m. carlson 2018-12-04 19:29 ` Jonathan Tan 2018-12-05 5:02 ` Junio C Hamano 2018-12-05 5:55 ` Junio C Hamano 2018-12-06 23:16 ` Jonathan Tan 2018-12-03 23:37 ` [WIP RFC 3/5] upload-pack: refactor reading of pack-objects out Jonathan Tan 2018-12-04 0:30 ` Stefan Beller 2018-12-05 6:30 ` Junio C Hamano 2018-12-03 23:37 ` [WIP RFC 4/5] upload-pack: refactor writing of "packfile" line Jonathan Tan 2018-12-06 6:35 ` Junio C Hamano 2018-12-06 23:25 ` Jonathan Tan 2018-12-07 0:22 ` Junio C Hamano 2018-12-03 23:37 ` [WIP RFC 5/5] upload-pack: send part of packfile response as uri Jonathan Tan 2018-12-04 20:09 ` Stefan Beller 2018-12-04 0:01 ` [WIP RFC 0/5] Design for offloading part of packfile response to CDN Stefan Beller
Reply instructions: You may reply publically 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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox