Git 1.7.12-rc1

The first release candidate for the upcoming Git 1.7.12 can be found at

    http://code.google.com/p/git-core/downloads/list

and also at the usual repositories.

Some highlights:

• An experimental support for UTF-8 pathnames on MacOS.
  I think there still are places that need conversion between the system encoding (UTF-8 normalized by decomposing) and the more commonly used encoding (precomposed) that is used internally for better interoperability, but this should be a good start.
• $HOME/.gitconfig file can be moved to $HOME/.config/git/config, in line with XDG.
  This will also allow $HOME/.config/git/attributes and $HOME/.config/git/ignore, if exist, to be automatically used as core.attributesfile and core.excludesfile, respectively.
• "git apply" learned the same three-way merge patch wiggling magic "git am" supports, via the "-3" option.
• "git rebase -i --root" learned how to update the root commit when requested.
• "git status" can give a more detailed explanation during "intermediate" state of multi-step operations, e.g. "merge", "rebase".
• A remote "SCM" interface to MediaWiki in contrib/ learned to handle file attachments.

Please test so that we can avoid regressions in the final release that will happen late August.

Thanks.

Git 1.7.11.4

The fourth maintenance release for 1.7.11.x series has been tagged and is available at

    http://code.google.com/p/git-core/downloads/list

It updates 1.7.11.3 with a handful of updates. The most notable one may be that you can now run filter-branch across a commit whose committer timestamp is in year 1970 (more precisely, the UNIX epoch).

Git 1.7.12-rc0

A release-candidate preview for the upcoming 1.7.12 has been tagged. The release tarballs are found at:

    http://code.google.com/p/git-core/downloads/list

as usual.

Git v1.7.12 Release Notes (draft)

Updates since v1.7.11

UI, Workflows & Features

• Git can be told to normalize pathnames it read from readdir(3) and all arguments it got from the command line into precomposed UTF-8 (assuming that they come as decomposed UTF-8), in order to work around issues on Mac OS.
• I think there still are other places that need conversion (e.g. paths that are read from stdin for some commands), but this should be a good first step in the right direction.
• Per-user $HOME/.gitconfig file can optionally be stored in $HOME/.config/git/config instead, which is in line with XDG.
• The value of core.attributesfile and core.excludesfile default to $HOME/.config/attributes and $HOME/.config/ignore respectively when these files exist.
• Logic to disambiguate abbreviated object names have been taught to take advantage of object types that are expected in the context, e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a commit object, not a blob nor a tree.  This will help us prolong the lifetime of abbreviated object names.
• "git apply" learned to wiggle the base version and perform three-way merge when a patch does not exactly apply to the version you have.
• Scripted Porcelain writers now have access to the credential API via the "git credential" plumbing command.
• "git clone --local $path" started its life as an experiment to optionally use link/copy when cloning a repository on the disk, but we didn't deprecate it after we made the option a no-op to always use the optimization.  The command learned "--no-local" option to turn this off, as a more explicit alternative over use of file:// URL.
• "git fetch" and friends used to say "remote side hung up unexpectedly" when they failed to get response they expect from the other side, but one common reason why they don't get expected response is that the remote repository does not exist or cannot be read. The error message in this case was updated to give better hints to the user.
• "git help -w $cmd" can show HTML version of documentation for "git-$cmd" by setting help.htmlpath to somewhere other than the default location where the build procedure installs them locally; the variable can even point at a http:// URL.
• "git rebase [-i] --root $tip" can now be used to rewrite all the history leading to "$tip" down to the root commit.
• "git rebase -i" learned "-x " to insert "exec " after each commit in the resulting history.
• "git status" gives finer classification to various states of paths in conflicted state and offer advice messages in its output.
• "git submodule" learned to deal with nested submodule structure where a module is contained within a module whose origin is specified as a relative URL to its superproject's origin.
• A rather heavy-ish "git completion" script has been split to create a separate "git prompting" script, to help lazy-autoloading of the completion part while making prompting part always available.
• "gitweb" pays attention to various forms of credits that are similar to "Signed-off-by:" lines in the commit objects and highlights them accordingly.

Foreign Interface

• "mediawiki" remote helper (in contrib/) learned to handle file attachments.
• "git p4" now uses "Jobs:" and "p4 move" when appropriate.
• vcs-svn has been updated to clean-up compilation, lift 32-bit limitations, etc.

Performance, Internal Implementation, etc. (please report possible regressions)

• Some tests showed false failures caused by a bug in ecryptofs.
• We no longer use AsciiDoc7 syntax in our documentation and favor a more modern style.
• "git am --rebasing" codepath was taught to grab authorship, log message and the patch text directly out of existing commits.  This will help rebasing commits that have confusing "diff" output in their log messages.
• "git index-pack" and "git pack-objects" use streaming API to read from the object store to avoid having to hold a large blob object in-core while they are doing their thing.
• Code to match paths with exclude patterns learned to avoid calling fnmatch() by comparing fixed leading substring literally when possible.
• "git log -n 1 -- rarely-touched-path" was spending unnecessary cycles after showing the first change to find the next one, only to discard it.

Also contains minor documentation updates and code clean-ups.

Fixes since v1.7.11

Unless otherwise noted, all the fixes since v1.7.11 in the maintenance releases are contained in this release (see release notes to them for details).

• "git commit-tree" learned a more natural "-p " order of arguments long time ago, but recently forgot it by mistake.  (merge 4b7518a kk/maint-commit-tree later to maint).
• "git diff --no-ext-diff" did not output anything for a typechange filepair when GIT_EXTERNAL_DIFF is in effect.  (merge c12f82a jv/maint-no-ext-diff later to maint).
• When "git am" failed, old timers knew to check .git/rebase-apply/patch to see what went wrong, but we never told the users about it.  (merge 14bf2d5 pg/maint-1.7.9-am-where-is-patch later to maint).
• When "git submodule add" clones a submodule repository, it can get confused where to store the resulting submodule repository in the superproject's .git/ directory when there is a symbolic link in the path to the current directory.  (merge 6eafa6d jl/maint-1.7.10-recurse-submodules-with-symlink later to maint).
• In 1.7.9 era, we taught "git rebase" about the raw timestamp format but we did not teach the same trick to "filter-branch", which rolled a similar logic on its own.  (merge 44b85e89 jc/maint-filter-branch-epoch-date later to maint).

Git 1.7.11.3

The third maintenance release for 1.7.11 has been tagged and is available at the usual places (see Git Public Repositories link).

• The error message from "git push $there :bogo" (and its equivalent "git push $there --delete bogo") mentioned that we tried and failed to guess what ref is being deleted based on the LHS of the refspec, which we don't.
• A handful of files and directories we create had tighter than necessary permission bits when the user wanted to have group writability (e.g. by setting "umask 002").
• "commit --amend" used to refuse amending a commit with an empty log message, with or without "--allow-empty-message".
• "git commit --amend --only --" was meant to allow "Clever" people to rewrite the commit message without making any change even when they have already changes for the next commit added to their index, but it never worked as advertised since it was introduced in 1.3.0 era.
• Even though the index can record pathnames longer than 1<<12 bytes, in some places we were not comparing them in full, potentially replacing index entries instead of adding.
• "git show"'s auto-walking behaviour was an unreliable and unpredictable hack; it now behaves just like "git log" does when it walks.
• "git diff", "git status" and anything that internally uses the comparison machinery was utterly broken when the difference involved a file with "-" as its name.  This was due to the way "git diff --no-index" was incorrectly bolted on to the system, making any comparison that involves a file "-" at the root level incorrectly read from the standard input.
• We did not have test to make sure "git rebase" without extra options filters out an empty commit in the original history.
• "git fast-export" produced an input stream for fast-import without properly quoting pathnames when they contain SPs in them.
• "git checkout --detach", when you are still on an unborn branch, should be forbidden, but it wasn't.
• Some implementations of Perl terminates "lines" with CRLF even when the script is operating on just a sequence of bytes.  Make sure to use "$PERL_PATH", the version of Perl the user told Git to use, in our tests to avoid unnecessary breakages in tests.

The release tarballs are found at:

http://code.google.com/p/git-core/downloads/list

On the 'master' front, we are getting very close to the next feature release 1.7.12.

Git 1.7.11.2

The second maintenance release for 1.7.11 has many real fixes (the first one was mainly to fix the HTML formatted documentation pages) to bugs identified, diagnosed and fixed in the past three weeks. These fixes have been cooking on the master front for some time.

• On Cygwin, the platform pread(2) is not thread safe, just like our own compat/ emulation, and cannot be used in the index-pack program.  Makefile variable NO_THREAD_SAFE_PREAD can be defined to avoid use of this function in a threaded program.
• "git add" allows adding a regular file to the path where a submodule used to exist, but "git update-index" does not allow an equivalent operation to Porcelain writers.
• "git archive" incorrectly computed the header checksum; the symptom was observed only when using pathnames with hi-bit set.
• "git blame" did not try to make sure that the abbreviated commit object names in its output are unique.
• Running "git bundle verify" on a bundle that records a complete history said "it requires these 0 commits".
• "git clone --single-branch" to clone a single branch did not limit the cloning to the specified branch.
• "git diff --no-index" did not correctly handle relative paths and did not correctly give exit codes when run under "--quiet" option.
• "git diff --no-index" did not work with pagers correctly.
• "git diff COPYING HEAD:COPYING" gave a nonsense error message that claimed that the treeish HEAD did not have COPYING in it.
• When "git log" gets "--simplify-merges/by-decoration" together with "--first-parent", the combination of these options makes the simplification logic to use in-core commit objects that haven't been examined for relevance, either producing incorrect result or taking too long to produce any output.  Teach the simplification logic to ignore commits that the first-parent traversal logic ignored when both are in effect to work around the issue.
• "git ls-files --exclude=t -i" did not consider anything under t/ as excluded, as it did not pay attention to exclusion of leading paths while walking the index.  Other two users of excluded() are also updated.
• "git request-pull $url dev" when the tip of "dev" branch was tagged with "ext4-for-linus" used the contents from the tag in the output but still asked the "dev" branch to be pulled, not the tag.

As usual, the release tarballs are found at:

http://code.google.com/p/git-core/downloads/list

and the following public repositories all have a copy of the v1.7.11.2 tag and the maint branch that the tag points at:

url = git://repo.or.cz/alt-git.git

url = https://code.google.com/p/git-core/

url = git://git.sourceforge.jp/gitroot/git-core/git.git

url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core

url = https://github.com/gitster/git

Git 1.7.11.1

It is a bit embarrassing but it turns out that all cross links in the HTML version of manual pages in Git 1.7.11 were missing, so a brown-paper-bag maintenance release 1.7.11.1 is out.

Git 1.7.10.4 and Git 1.7.11-rc1

All the fixes to 1.7.10.x maintenance track that have been cooking on the master branch have also been merged and 1.7.10.4 release has been pushed out. Hopefully this will be the last release from the 1.7.10.x track. For the list of changes in this release, please see its release notes.


Finally 1.7.11-rc1 has been tagged. We originally wanted to keep this cycle on the shorter side of the 8-10 week release cycle, so that the end of the next cycle would coincide better with the end of GSoC, but it appears that it is looking like somewhat a lost cause. In any case, this marks the end of feature tweaks and bugfixes in this cycle and the focus shifts to finding and fixing regressions introduced since 1.7.10.

Please download, build and test the release candidate so that users do not have to suffer from regressions in the final 1.7.11 release.

Git 1.7.10.3 and Git 1.7.11-rc0

Two releases for a day.

The third maintenance release for 1.7.10.X series fixes a handful of regressions in previous 1.7.10.X releases.

On the master front, 1.7.11-rc0 is out.  Treat it as a preview of the real release candidate for the next big release—there still are several topics cooking in the next branch to shake out possible new bugs to make sure we can have a solid 1.7.11 release.

The most notable, from the long-term point of view, is the introduction of the simple push mode (credit goes to Matthieu Moy), which would hopefully prove to be a good default for new users until they configure the push.default to suit the requirement of their project.  With this, running git push or git push origin without saying which branches and/or tags to update what on the remote side from either command line or from the remote.$name.push configuration will only push the current branch to the branch of the same name on the other side, but only if the current branch is configured to use the branch on the other side as its upstream.

Have fun.

Git 1.7.10.1

The first maintenance release for 1.7.10.x series is out.



Git v1.7.10.1 Release Notes
===========================


Additions since v1.7.10
-----------------------


Localization message files for Danish and German have been added.




Fixes since v1.7.10
-------------------


 * "git add -p" is not designed to deal with unmerged paths but did
   not exclude them and tried to apply funny patches only to fail.


 * "git blame" started missing quite a few changes from the origin
   since we stopped using the diff minimalization by default in v1.7.2
   era.


 * When PATH contains an unreadable directory, alias expansion code
   did not kick in, and failed with an error that said "git-subcmd"
   was not found.


 * "git clean -d -f" (not "-d -f -f") is supposed to protect nested
   working trees of independent git repositories that exist in the
   current project working tree from getting removed, but the
   protection applied only to such working trees that are at the
   top-level of the current project by mistake.


 * "git commit --author=$name" did not tell the name that was being
   recorded in the resulting commit to hooks, even though it does do
   so when the end user overrode the authorship via the
   "GIT_AUTHOR_NAME" environment variable.


 * When "git commit --template F" errors out because the user did not
   touch the message, it claimed that it aborts due to "empty
   message", which was utterly wrong.


 * The regexp configured with diff.wordregex was incorrectly reused
   across files.


 * An age-old corner case bug in combine diff (only triggered with -U0
   and the hunk at the beginning of the file needs to be shown) has
   been fixed.


 * Rename detection logic used to match two empty files as renames
   during merge-recursive, leading to unnatural mismerges.


 * The parser in "fast-import" did not diagnose ":9" style references
   that is not followed by required SP/LF as an error.


 * When "git fetch" encounters repositories with too many references,
   the command line of "fetch-pack" that is run by a helper
   e.g. remote-curl, may fail to hold all of them. Now such an
   internal invocation can feed the references through the standard
   input of "fetch-pack".


 * "git fetch" that recurses into submodules on demand did not check
   if it needs to go into submodules when non branches (most notably,
   tags) are fetched.


 * "log -p --graph" used with "--stat" had a few formatting error.


 * Running "notes merge --commit" failed to perform correctly when run
   from any directory inside $GIT_DIR/.  When "notes merge" stops with
   conflicts, $GIT_DIR/NOTES_MERGE_WORKTREE is the place a user edits
   to resolve it.


 * The 'push to upstream' implementation was broken in some corner
   cases. "git push $there" without refspec, when the current branch
   is set to push to a remote different from $there, used to push to
   $there using the upstream information to a remote unreleated to
   $there.


 * Giving "--continue" to a conflicted "rebase -i" session skipped a
   commit that only results in changes to submodules.


Also contains minor fixes and documentation updates.

Naming a machine

When I came to Google, I asked my desktop machine to be named "linus". I was asked: "Do you really want your machine named linus?"

But the thing is, the requested name is not after Linus Torvalds. I name my machines using a dictionary. Let me explain how. I name my machines after some theme, and the machine "linus", just like my primary box "alter", is named after the primary activity I was planning to do on it, namely "Git".

The first thing to do is to find a bunch of dictionary words that have G, I and T in this order. We may find these words: afGhanIsTan, linGuIsT, aGlITter,...

Then remove these G, I and T from these dictionary words to obtain: afhansan, linus, alter,...

Finally, pick ones that can be pronounced and preferrably in dictionary.

That is how the machine was called "linus", and the primary box I use at home is "alter". My general purpose notebook is called "wing" (named after its manufacturer—can you guess who?).


Needless to say, I already know the name of my next Git machine: dial.

How do you name your machine?