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

1.5.4-rc2 plans

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 21, 2007, 00:32 UTC
Message-ID
<7vwsr8lwf7.fsf@gitster.siamese.dyndns.org>

I've tagged -rc1 last night. The changes are mostly fixes. There are some remaining issues I'd like to see fixed/decided before 1.5.4.

One important issue is to identify and fix regressions since 1.5.3 series. No "rewrite scripted git-foo completely in C" can be regression free, and we had quite a few internal changes during 1.5.4 cycle (not just rewrite to C, but C level uses new and improved API such as strbuf and parse-options). Currently I am aware of these regressions:

 * handling of options, "--abbrev 10 HEAD", "--abbrev=10 HEAD" and
   "--abbrev HEAD".  The last one does not work for commands that use
   parse-options.  Pierre is on top of this, I hope.
 * handling of EDITOR in git commit and git tag is currently different.
   It expects "vi" not "vi --some-funny-option".  I sent out a
   for-discussion patch after seeing Steven's and Luciano's.
but I am sure there must be others that we haven't even identified.

Also there have been handful usability issues, which can be solved without incompatible changes:

 * Should "git stash" stop doing anything useful?  I think the patch
   from Nana today may be a reasonable compromise, although I still
   think fundamentally different behaviour for the same command
   configurable per-user is not very nice (we have precedent in "git
   clean" already, though, but "git clean" is inherently dangerous
   command, and "git stash" is much more useful and the issue impacts
   more people).
 * Introduction of "<tree>:./path" (Dscho).  I could be talked into
   accepting the patch if it is useful to people who live deep within
   subdirectories.
 * Making commit log message cleansing optionally less aggressive.  I do
   not think we have seen the end of the thread yet, but I think Linus's
   "three cleansing levels" approach is on the right track.

I'd like to see the above resolved and hopefully 12 other regressions identified and fixed before the end of the year, when -rc2 can hopefully happen.

The following technical issues have been raised but not resolved and I do not expect the resolution to be part of 1.5.4.

 * Authenticated pserver (Ævar Arnfjörð Bjarmason).  It needs security
   audit of the code and also the password storage needs to be decided.
   This can wait post 1.5.4.
 * Threaded "repack -a -d -f" when having a verify tight pack suffers
   from massive malloc(3) memory fragmentation, which we cannot do much
   about.
 * Rebase using "format-patch | am" machinery has issues when dealing
   with a mostly-text change that includes NUL (or anything you cannot
   e-mail patch for).  The workaround is "rebase -m" which unfortunatly
   is slow.  I am working on rewriting cherry-pick whenever I find time
   to address it, though.
 * Handling of trailing blank lines does not mesh well with the way diff
   and apply whitespace logic is done.
Next: Johannes Sixt
Message 1 of 19 in “1.5.4-rc2 plans”
  1. Junio C HamanoDec 21, 2007
  2. Johannes SixtDec 21, 2007
  3. Mike FrysingerDec 21, 2007
  4. Johannes SchindelinDec 22, 2007
  5. Mike FrysingerDec 22, 2007
  6. Steven GrimmDec 21, 2007
  7. Pierre HabouzitDec 21, 2007
  8. git-tag: fix -l switch handling regression.Pierre Habouzit, Dec 21, 2007
  9. Junio C HamanoDec 21, 2007
  10. Pierre HabouzitDec 21, 2007
  11. Junio C HamanoDec 22, 2007
  12. Junio C HamanoDec 21, 2007
  13. Pierre HabouzitDec 21, 2007
  14. parse-options: Add a gitcli(5) man page.Pierre Habouzit, Dec 21, 2007
  15. Johannes SchindelinDec 22, 2007
  16. Pierre HabouzitDec 22, 2007
  17. Junio C HamanoDec 22, 2007
  18. Pierre HabouzitDec 22, 2007
  19. Junio C HamanoDec 22, 2007

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.