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

Re: [PATCH 0/6] Make 'git help everyday' work

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 10, 2014, 20:19 UTC
Message-ID
<20140110201957.GJ4776@google.com>
In-Reply-To
<1389309192-5748-1-git-send-email-philipoakley@iee.org>
Hi,
Philip Oakley wrote:
> The "Everyday GIT With 20 Commands Or So" guide is not accessible
> via the git help system. Fix that.
Neat. :)
Junio covered everything I'd want to say about patch 1/6.

After fixing that, I'd suggest squashing all 6 patches into a single patch. They all are part of accomplishing the same task, they are not too hard to read together, and the intermediate state after applying a few but not the rest doesn't make much sense. The details of patches 2-6/6 look good to me.

Alternatively, this could be two patches:
 1 - modify everyday.txt in place to be a suitable manpage
 2 - rename it, add a placeholder for the old name, and modify the
     build rules to treat it as an actual manpage

Hope that helps, Jonathan

Previous: Philip Oakley
Message 21 of 21 in “Make 'git help everyday' work”
  1. 0/6 Make 'git help everyday' workPhilip Oakley, Jan 9, 2014
  2. 1/6 copy everyday.txt to giteveryday.txtPhilip Oakley, Jan 9, 2014
  3. 2/6 Update giteveryday.txt to fit man page formattingPhilip Oakley, Jan 9, 2014
  4. 3/6 add giteveryday to the manpages make listPhilip Oakley, Jan 9, 2014
  5. 4/6 Add deprecation note to old everyday.txtPhilip Oakley, Jan 9, 2014
  6. 5/6 add 'everyday' to the help --guides listPhilip Oakley, Jan 9, 2014
  7. 6/6 Update git(1) link to giteverydayPhilip Oakley, Jan 9, 2014
  8. Junio C HamanoJan 9, 2014
  9. Philip OakleyJan 10, 2014
  10. Junio C HamanoJan 10, 2014
  11. Philip OakleyJan 10, 2014
  12. Philip OakleyJan 11, 2014
  13. Stefan NäweJan 10, 2014
  14. Philip OakleyJan 16, 2014
  15. Stefan NäweJan 17, 2014
  16. Philip OakleyJan 21, 2014
  17. Junio C HamanoJan 21, 2014
  18. Philip OakleyJan 22, 2014
  19. Junio C HamanoJan 22, 2014
  20. Philip OakleyJan 22, 2014
  21. Jonathan NiederJan 10, 2014

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.