git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.6.4-rc3
Date: Mon, 27 Jul 2009 07:13:11 +0200	[thread overview]
Message-ID: <20090727051311.GA17300@pengutronix.de> (raw)
In-Reply-To: <7vws5vrh93.fsf@alter.siamese.dyndns.org>

Hi Junio,

On Sun, Jul 26, 2009 at 01:16:40AM -0700, Junio C Hamano wrote:
> Updates since v1.6.3
> --------------------
> 
> [...]
> 
> (usability, bells and whistles)
> 
>  * "git add --edit" lets users edit the whole patch text to fine-tune what
>    is added to the index.
> 
>  * "git am" accepts StGIT series file as its input.
> 
>  * "git bisect skip" skips to a more randomly chosen place in the hope
>    to avoid testing a commit that is too close to a commit that is
>    already known to be untestable.
> 
>  * "git cvsexportcommit" learned -k option to stop CVS keywords expansion
> 
>  * "git grep" learned -p option to show the location of the match using the
>    same context hunk marker "git diff" uses.
> 
>  * https transport can optionally be told that the used client
>    certificate is password protected, in which case it asks the
>    password only once.
> 
>  * "git imap-send" is IPv6 aware.
> 
>  * "git log --graph" draws graphs more compactly by using horizontal lines
>    when able.
> 
>  * "git log --decorate" shows shorter refnames by stripping well-known
>    refs/* prefix.
> 
>  * "git push $name" honors remote.$name.pushurl if present before
>    using remote.$name.url.  In other words, the URL used for fetching
>    and pushing can be different.
> 
>  * "git send-email" understands quoted aliases in .mailrc files (might
>    have to be backported to 1.6.3.X).
> 
>  * "git send-email" can fetch the sender address from the configuration
>    variable "sendmail.from" (and "sendmail.<identity>.from").
> 
>  * "git show-branch" can color its output.
> 
>  * "add" and "update" subcommands to "git submodule" learned --reference
>    option to use local clone with references.
> 
>  * "git submodule update" learned --rebase option to update checked
>    out submodules by rebasing the local changes.
> 
>  * "gitweb" can optionally use gravatar to adorn author/committer names.
> 
I'm not really sure if it's worth to point out:

 * "git rev-parse" learned "--stop-at-non-option"

But on the other hand I sometimes want to find out the oldest release
supporting a certain feature.  Up to you to decide ...

> ---
> exec >/var/tmp/1
> echo O=$(git describe master)
> O=v1.6.4-rc2-31-g2ceb639
> git shortlog --no-merges $O..master ^maint
Is it intended that this occurs in the mail?  (Oh, a possible symlink
attack :-)

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

      parent reply	other threads:[~2009-07-27  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26  8:16 [ANNOUNCE] GIT 1.6.4-rc3 Junio C Hamano
2009-07-27  1:54 ` Chris Hills
2009-07-27  3:14   ` Junio C Hamano
2009-07-27  5:13 ` Uwe Kleine-König [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090727051311.GA17300@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).