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

[ANNOUNCE] GIT 0.99.7

From
Junio C Hamano <junkio@cox.net>
Date
Sep 18, 2005, 23:37 UTC
Message-ID
<7vwtleyml5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vr7c02zgg.fsf@assigned-by-dhcp.cox.net>

I am hoping that sending this out to the kernel list is not considered too much of useless spamming, but I promise I wouldn't do thit next time for 0.99.8, if I hear from somebody not to.

Here comes GIT 0.99.7
--

Done in 0.99.7 ==============

Organization ~~~~~~~~~~~~

Some commands and most scripts are renamed for consistency.
  - We have an official standard terminology list [*1*].  To
    match this, commands that operate on index files now have
    'index' instead of 'cache' in their names, and ones that
    download are called 'fetch' instead of 'pull'.
  - We used to install most of the commands that happen to be
    implemented as scripts as 'git-*-script', which was
    cumbersome to remember and type unless you always used 'git'
    wrapper.  They lost '-script' suffix from their names.

For now, we install synonyms as symbolic links so that old names continue to work, but they are planned to be removed in 0.99.8 (or later if there are enough objections on the list -- so far I have heard none).

Also ancient environment variables [*2*] are not supported anymore.

New Features and Commands ~~~~~~~~~~~~~~~~~~~~~~~~~

Downloaders that are not fully git aware have been taught about the mechanism to borrow objects from other repositories via objects/info/alternates the server side may be using. 'git fetch' and 'git pull' commands over rsync and http transport should be able to handle such repositories [*3*].

People found interesting cases where the 'stupid' three-way merge mechanism does the wrong thing without noticing. We have two new merge algorithms by Daniel and Fredrik that attempt to do better in such cases. A new 'git merge' command has been introduced to make it easier to experiment with and choose among different merge strategies. Note that 'git pull' still uses the traditional three-way merge after downloading, but it is expected to be switched to use 'git merge' sometime in the future.

Importing from tla archives has been improved and documentated.

'git branch' command acquired '-d' flag to delete a branch that has already been merged into the current branch.

'git bisect' command is easier to use by logging the earlier good/bad choices and make it replayable.

'git repack' has -a' flag to pack the whole repository into a single pack.

'git grep' is a new command to run grep on files 'git' knows about.

Fixes ~~~~~

* 'git-diff-*' commands used to mark copy/rename incorrectly
  when an (A,B) => (B,C) rename was made.  We said the new B is
  a copy of old A, not a rename of old A.
* When the user exported CDPATH into environment, 'cd' took
  scripts to unexpected places.  Unset it upfront to guard us.
* 'git format-patch' knows about 'git cherry' and skips patches
  already merged upstream.
* hopefully plugged memory leak in diffcore-rename properly.
* commit walkers incorrectly assumed having a commit means we
  have the whole history leading up to it -- which is not true
  if the previous download was interrupted.  As a safety
  measure, we now only trust the commits that are pointed by the
  existing refs.
* 'git rev-list' uses a lot less memory.
* The build should be a bit friendlier to Solaris and Darwin now.
* 'git ssh-{push,pull}' are friendlier to tcsh.
* http transport is nicer to caching proxies.
* 'git daemon' port is registered with IANA.
* Many documentation updates.

[Footnotes] *1* http://www.kernel.org/pub/software/scm/git/docs/glossary.html

*2* Ancient environment variable names: SHA1_FILE_DIRECTORIES AUTHOR_DATE AUTHOR_EMAIL AUTHOR_NAME COMMIT_AUTHOR_EMAIL COMMIT_AUTHOR_NAME SHA1_FILE_DIRECTORY

*3* But not grafts.
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 28 in “GIT 0.99.6”
  1. Junio C HamanoSep 8, 2005
  2. Tool renames and 'ls-files -t' outputJunio C Hamano, Sep 8, 2005
  3. Post 0.99.7 preperation patchesJunio C Hamano, Sep 9, 2005
  4. Petr BaudisSep 12, 2005
  5. RFC: s/git-merge-base/git-find-common-ancestor/gYasushi SHOJI, Sep 11, 2005
  6. Junio C HamanoSep 11, 2005
  7. Rename git-merge-base to git-find-merge-baseYasushi SHOJI, Sep 11, 2005
  8. Tool rename fallout fixJunio C Hamano, Sep 9, 2005
  9. No GIT 0.99.7 todayJunio C Hamano, Sep 17, 2005
  10. [ANNOUNCE] GIT 0.99.7Junio C Hamano, Sep 18, 2005
  11. What to expect after GIT 0.99.7Junio C Hamano, Sep 18, 2005
  12. Linus TorvaldsSep 19, 2005
  13. Linus TorvaldsSep 19, 2005
  14. Johannes SchindelinSep 19, 2005
  15. Joachim B HagaSep 19, 2005
  16. Linus TorvaldsSep 19, 2005
  17. Anton AltaparmakovSep 19, 2005
  18. Matthias UrlichsSep 19, 2005
  19. Junio C HamanoSep 19, 2005
  20. Petr BaudisSep 19, 2005
  21. Linus TorvaldsSep 19, 2005
  22. [ANNOUNCE] Cogito-0.15Petr Baudis, Sep 19, 2005
  23. Pavel MachekSep 19, 2005
  24. Petr BaudisSep 20, 2005
  25. Linus TorvaldsSep 20, 2005
  26. Nigel CunninghamSep 19, 2005
  27. Chris WhiteSep 19, 2005
  28. Alan ChandlerSep 19, 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.