git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/WIP 1/2] Documentation: fix minor inconsistency

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 23, 2009, 14:56 UTC
Message-ID
<49C7A326.2050403@drmicha.warpmail.net>
In-Reply-To
<vpq7i2g9u4m.fsf@bauges.imag.fr>
Matthieu Moy venit, vidit, dixit 23.03.2009 15:44:
Show 9 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> 
>> While we don't always write out commands in full (`git command`) we
>> should do it consistently in adjacent paragraphs.
> 
>> -	If set to true or "refuse", receive-pack will deny a ref update
>> +	If set to true or "refuse", git-receive-pack will deny a ref update
> 
> Then, shouldn't this be `git receive-pack` ?

It should be git-receive-pack in the first patch (adding missing git in the same style as used there), `git-receive-pack` in the second patch (implementation of step 1) and `git receive-pack` in step 2 (the un-dashifying step), which comes later, just as outlined in the cover letter. Mixing these steps into one patch would be a reviewing nightmare. Squashing those two patches (constituting step 1 for the first few files) would be fine.

Michael
Previous: Matthieu MoyNext: Michael J Gruber
Message 5 of 11 in “[RFC/WIP 0/2] Documentation clean-up: git commands”
  1. Michael J GruberMar 23, 2009
  2. 1/2 Documentation: fix minor inconsistencyMichael J Gruber, Mar 23, 2009
  3. 2/2 Documentation: format git commands consistentlyMichael J Gruber, Mar 23, 2009
  4. Matthieu MoyMar 23, 2009
  5. Michael J GruberMar 23, 2009
  6. Michael J GruberMar 23, 2009
  7. Junio C HamanoMar 23, 2009
  8. Michael J GruberMar 23, 2009
  9. Chris JohnsenMar 23, 2009
  10. Jeff KingMar 24, 2009
  11. Michael J GruberMar 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.