Re: Using the --track option when creating a branch

From: Andreas Ericsson <ae@op5.se>
Date: Oct 30, 2008, 14:54 UTC
Message-ID: <4909CABD.1040708@op5.se>
In-Reply-To: <2008-10-30-15-23-16+trackit+sam@rfc1149.net>

Samuel Tardieu wrote:

Show 21 quoted lines

> * Andreas Ericsson <ae@op5.se> [2008-10-30 15:06:16 +0100]
> 
>> --all pushes all refs, even the non-matching ones, which is very
>> rarely desirable and only accidentally sometimes the same as "push all
>> matching refs".
>>
>>> I know that I've never had the intent to push all the refs without
>>> thinking about it first. Most of the time, I intend to push only
>>> the current branch I am in.
>> Then say so. There's a very simple command syntax for it:
>> "git push <remote> <current-branch>"
> 
> I update the branches I'm working in maybe 20 times a day, sometimes
> more. When I make a change and all the tests pass, I prefer to call
> 
>   git push
> 
> rather than
> 
>   git push origin 2.0-beta1
>

So why don't you? Unless you also make lots of changes on other branches, the two commands will result in exactly the same thing.

Show 9 quoted lines

> (and "2.0-beta1" is a short name here, some branches have much longer
> names)
> 
> I think it would be better to have :
> 
>   git push                <= push the current branch
>   git push --all          <= push all matching refs
>   git push --all --create <= push all matching refs, create if needed
>

Correct me if I'm wrong, but wouldn't my suggestion of not trying to push (even matching) branches that haven't been updated since we last fetched from the remote do exactly the same thing for your particular use-case, but without syntax change and all the annoying minor parts that it entails?

Show 7 quoted lines

> The latest command is probably used so rarely (compared to the others)
> that it wouldn't be a problem to make it longer. Of course, if a
> refspec is given explicitely, it should be honored and remote refs
> created if needed.
> 
> I am curious of what other people workflows are. Do you often push
> multiple branches at the same time?

Quite often, yes.

> More often than one at a time?

No.

> Many times a day?
>

Define "many". Perhaps as often as 2-3 times per day. Not very often, but frequent enough that I definitely want some short sweet way of doing it. OTOH, I also find the "rejected" messages annoying, and I definitely feel one could do something about them. However, it's my birthday today and I plan on being far too drunk/hungover the entire weekend for me to take any actions in that direction.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231