Re: What's cooking in git.git (Feb 2014, #04; Wed, 12)

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Feb 14, 2014, 19:31 UTC
Message-ID: <20140214193131.GI4582@vauxhall.crustytoothpaste.net>
In-Reply-To: <xmqqd2ism1pu.fsf@gitster.dls.corp.google.com>

On Wed, Feb 12, 2014 at 01:59:41PM -0800, Junio C Hamano wrote:

Show 17 quoted lines

> * bc/gpg-sign-everywhere (2014-02-11) 9 commits
>  - pull: add the --gpg-sign option.
>  - rebase: add the --gpg-sign option
>  - rebase: parse options in stuck-long mode
>  - rebase: don't try to match -M option
>  - rebase: remove useless arguments check
>  - am: add the --gpg-sign option
>  - am: parse options in stuck-long mode
>  - git-sh-setup.sh: add variable to use the stuck-long mode
>  - cherry-pick, revert: add the --gpg-sign option
> 
>  Teach "--gpg-sign" option to many commands that create commits.
> 
>  Changes to some scripted Porcelains use unsafe variable
>  substitutions and still need to be tightened.
> 
>  Will merge to 'next'.

Junio, did you want a reroll with that fixed commit message, or will you fix it up yourself?

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187