On Wed, Mar 07, 2012 at 05:35:07PM -0800, Junio C Hamano wrote:
> * A content filter (clean/smudge) used to be just a way to make the
> recorded contents "more useful", and allowed to fail; a filter can
> new optionally be marked as "required".
s/new/now/
> * "git am" learned to pass "-b" option to underlying "git mailinfo", so
> that bracketed string other than "PATCH" at the beginning can be kept.
s/bracketed/a &/
(or s/string/&s/)
> * "git clone" learned to detach the HEAD in the resulting repository
> when the source repository's HEAD does not point to a branch.
Hmm. Hasn't this been the case for a while? The jk/clone-detached topic
went into v1.7.7, and it was just fixes for some corner cases; actually
writing a detached HEAD is much older than that, even.
I assume this entry is due to the nd/clone-detached topic. Reading over
those commits, it seems like it is more about properly checking the
"--branch" argument for being detached, so we can handle
"--branch=v1.0". So maybe:
* "git clone" learned to detach the HEAD in the resulting repository
when the user specifies a tag with "--branch" (e.g., "--branch=v1.0").
Clone also learned to print the usual "detached HEAD" advice in such
a case, similar to "git checkout v1.0".
> * "git log -G" learned to pay attention to the "-i" option and can
> find patch hunks that introduce or remove a string that matches the
> given pattern ignoring the case.
This didn't parse well for me. Also, it affects -S, too, doesn't it?
Maybe:
* "git log -G" and "git log -S" learned to pay attention to the "-i"
option. When "-i" is given, their patterns will match
case-insensitively.
> * The advise message given when the user didn't give enough clue on
> what to merge to "git pull" and "git merge" has been updated to
> be more concise and easier to understand.
s/advise/advice/
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html