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

What's in git.git (Mar 2009, #02; Thu, 05)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 5, 2009, 10:07 UTC
Message-ID
<7vfxhs2shk.fsf@gitster.siamese.dyndns.org>

The release is out, and immediately after that somebody spots a minor bug.

If things go as planned, tomorrow we will see a mass graduation to the master branch of topics that have been cooking in next during the pre release freeze period.

* The 'maint' branch has these fixes since v1.6.2
John Tapsell (1):
  Make the 'lock file' exists error more informative
Junio C Hamano (1):
  Beginning of 1.6.2 maintenance track
* The 'master' branch has these since v1.6.2 in addition to the above.
Carlos Manuel Duclos Vergara (1):
  git-archive: add --output=<file> to send output to a file
Christian Couder (1):
  rev-list: estimate number of bisection step left
Jeff King (1):
  improve missing repository error message
John Tapsell (3):
  Modify description file to say what this file is
  Google has renamed the imap folder
  Improve error message for git-filter-branch
Keith Cascio (2):
  Use DIFF_XDL_SET/DIFF_OPT_SET instead of raw bit-masking
  Fix neglect of diff_setup()/diff_setup_done() symmetry.
Next: René Scharfe
Message 1 of 13 in “What's in git.git (Mar 2009, #02; Thu, 05)”
  1. Junio C HamanoMar 5, 2009
  2. René ScharfeMar 7, 2009
  3. 1/4 parseopt: add PARSE_OPT_KEEP_UNKNOWNRené Scharfe, Mar 8, 2009
  4. Junio C HamanoMar 8, 2009
  5. Junio C HamanoMar 8, 2009
  6. 5/4 parseopt: document KEEP_ARGV0, KEEP_UNKNOWN, NO_INTERNAL_HELPRené Scharfe, Mar 9, 2009
  7. 6/4 parseopt: prevent KEEP_UNKNOWN and STOP_AT_NON_OPTION from being used togetherRené Scharfe, Mar 9, 2009
  8. 2/4 parseopt: add PARSE_OPT_NO_INTERNAL_HELPRené Scharfe, Mar 8, 2009
  9. 3/4 parseopt: make usage optionalRené Scharfe, Mar 8, 2009
  10. Junio C HamanoMar 8, 2009
  11. René ScharfeMar 9, 2009
  12. 4/4 archive: use parseopt for local-only optionsRené Scharfe, Mar 8, 2009
  13. Junio C HamanoMar 8, 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.