Re: [PATCH] git-cherry: make <upstream> parameter optional

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Dec 30, 2008, 13:13 UTC
Message-ID: <alpine.DEB.1.00.0812301411480.30769@pacific.mpi-cbg.de>
In-Reply-To: <200812291845.20500.markus.heidelberg@web.de>

Hi,

On Mon, 29 Dec 2008, Markus Heidelberg wrote:

Show 8 quoted lines

> The upstream branch <upstream> now defaults to the first tracked
> remote branch, which is set by the configuration variables
> branch.<name>.remote and branch.<name>.merge of the current branch.
> 
> Without such a remote branch, the command "git cherry [-v]" fails with
> usage output as before and an additional message.
> 
> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>

This would be a massively visible user interface change. At the moment, it does this (which I like):

	$ git cherry-pick
	usage: git cherry-pick [options] <commit-ish>

	    -n, --no-commit       don't automatically commit
	    -e, --edit            edit the commit message
	    -x                    append commit name when cherry-picking
	    -r                    no-op (backward compatibility)
	    -s, --signoff         add Signed-off-by:
	    -m, --mainline <n>    parent number

Opposed, Dscho