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

Last mile for 1.0

From
Junio C Hamano <junkio@cox.net>
Date
Jun 5, 2005, 23:21 UTC
Message-ID
<7vk6l8xue5.fsf_-_@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.58.0506051509490.1876@ppc970.osdl.org>
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:

LT> You document the "rename" header as being "rename from/to", which is LT> sensible, but doesn't match reality. diff.c has "rename old/new". I found LT> that out the hard way when doing git-apply ;)

The document was cut & paste from the version of apply.c before you found it out "the hard way", so of course its wording is sensible ;-) Anyway, I think we settled this part.

There are still some remaining issues before 1.0. The ones I personally would want to see merged and/or addressed are:

 - git-ssh-push documentation updates from Dan Barkalow, which
   he mentions in *1*.  I am the primarily guilty one about
   "other people seem to have missed it".
 - "-w heads/master heads/master" extension to the pull family,
   again from Dan, mentioned in the same message.
 - "--merge-order" extension to the git-rev-list, from Jon
   Seymour, last posted as *2*.  I have not tried it on
   something big (like linux-2.6 repository) and cannot vouch
   for its correctness myself, but I find what it claims to do
   quite sensible and attractive.
 - Tutorials you have been working on.  I'd appreciate it if my
   earlier "what about cvs annotate" example *3* finds its home
   somewhere in that document ;-).
 - "What happens when a merge goes wrong" helper script Jeff
   wanted to have in *4*.
 - Documentation from Jason McMullan for more commands, reminded
   by Petr Baudis in *5*.
[References]
*1* <Pine.LNX.4.21.0506031927000.30848-100000@iabervon.org>
*2* <20050605134733.3123.qmail@blackcubes.dyndns.org>
*3* <7vll5s35pd.fsf@assigned-by-dhcp.cox.net>
*4* <42A181C1.3010902@pobox.com>
*5* <20050605204739.GR17462@pasky.ji.cz>
Previous: Linus TorvaldsNext: Junio C Hamano
Message 6 of 25 in “Documentation: describe git extended diff headers.”
  1. Documentation: describe git extended diff headers.Junio C Hamano, Jun 5, 2005
  2. Linus TorvaldsJun 5, 2005
  3. Fix diff.c to match rename extended header to the document.Junio C Hamano, Jun 5, 2005
  4. Fix apply.c to match rename extended header to the document.Junio C Hamano, Jun 5, 2005
  5. Linus TorvaldsJun 5, 2005
  6. Last mile for 1.0Junio C Hamano, Jun 5, 2005
  7. Junio C HamanoJun 5, 2005
  8. McMullan, JasonJun 6, 2005
  9. Linus TorvaldsJun 6, 2005
  10. git-whatchanged vs "cvs annotate"Junio C Hamano, Jun 6, 2005
  11. Thomas GlanzmannJun 6, 2005
  12. Linus TorvaldsJun 6, 2005
  13. Junio C HamanoJun 6, 2005
  14. Linus TorvaldsJun 6, 2005
  15. Thomas GlanzmannJun 6, 2005
  16. Linus TorvaldsJun 6, 2005
  17. Thomas GlanzmannJun 6, 2005
  18. Junio C HamanoJun 6, 2005
  19. Linus TorvaldsJun 6, 2005
  20. Junio C HamanoJun 6, 2005
  21. Linus TorvaldsJun 6, 2005
  22. Linus TorvaldsJun 6, 2005
  23. 3-way read-tree case matrix.Junio C Hamano, Jun 8, 2005
  24. Junio C HamanoJun 8, 2005
  25. Tests: read-tree -m test updates.Junio C Hamano, Jun 8, 2005

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.