Re: What's cooking in git.git (topics)

From: Steffen Prohaska <prohaska@zib.de>
Date: Nov 12, 2007, 14:27 UTC
Message-ID: <087FCF8E-74BF-42EA-B7E2-4622DD0F5F9B@zib.de>
In-Reply-To: <Pine.LNX.4.64.0711121203150.4362@racer.site>

On Nov 12, 2007, at 1:21 PM, Johannes Schindelin wrote:

Show 13 quoted lines

>> * sp/refspec-match (Sun Nov 11 15:01:48 2007 +0100) 4 commits
>>  - refactor fetch's ref matching to use refname_match()
>>  - push: use same rules as git-rev-parse to resolve refspecs
>>  - add refname_match()
>>  - push: support pushing HEAD to real branch name
>>
>> This changes the semantics slightly but I think it is a move in
>> the right direction.
>
> We could add a "--matching" option and output a warning when it is not
> passed.  I would like this pretty soon, and would not be sad if it  
> went
> into 'next' before this topic.

Is this the road towards
1) "git push --matching" push matching branches.
2) "git push --current" push only current branch.
3) "git push" report error if the config does not contain a Push line.
    (after it reported a warning for a while).

I'd like to see this too. Unfortunately it's unlikely that I'll start working on it before next weekend.

"--matching" would be a no-op at this time. Only a warning would be printed if it is missing. Right?

	Steffen