git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Tapsell <johnflux@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Peter Krefting <peter@softwolves.pp.se>, git@vger.kernel.org
Subject: Re: Not pushing all branches?
Date: Fri, 13 Mar 2009 12:37:42 +0000	[thread overview]
Message-ID: <43d8ce650903130537r2459e1d2pef8fffc1c9b3fa5e@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903131149200.10279@pacific.mpi-cbg.de>

2009/3/13 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> Hi,
>
> On Fri, 13 Mar 2009, John Tapsell wrote:
>
>> 2009/3/13 Peter Krefting <peter@softwolves.pp.se>:
>>
>> > Doing "git push remote" pushes all my local branches by default. Is
>> > there a way to set it to *not* do that, and (for this particular
>> > remote repository) just push the current branch?
>>
>> > Or failing that, not allow me to run "git push" without specifying a
>> > branch?
>>
>> I've been pushing for this behaviour, and there was a patch a few days
>> ago to do this.  I'm not sure if it is/will be committed.
>
> As Junio is a careful maintainer, he will not change anything radical
> which would piss of a lot of people _without_ a proper, long-term plan
> that gives users a chance.
>
> I know, I once tried to push for something like that, and I am glad that
> Junio is too wise as to make Git unstable for existing users.

Understandable.  There were 6 patches, only the last one changes the
default.  Hopefully the first 5 will be applied and the 6 will
debated, then grudgingly applied :-)

John

  reply	other threads:[~2009-03-13 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13  7:48 Not pushing all branches? Peter Krefting
2009-03-13  8:12 ` Imran M Yousuf
2009-03-13  9:44   ` Peter Krefting
2009-03-13 10:49     ` Johannes Schindelin
2009-03-13 11:38     ` Finn Arne Gangstad
2009-03-13  8:25 ` John Tapsell
2009-03-13 10:51   ` Johannes Schindelin
2009-03-13 12:37     ` John Tapsell [this message]
2009-03-13 13:53       ` Johannes Schindelin
2009-03-13 13:56         ` John Tapsell
2009-03-13 15:48           ` Michael J Gruber
2009-03-13 16:00           ` Johannes Schindelin
2009-03-13 20:02   ` Junio C Hamano
2009-03-14  1:08     ` Miles Bader
2009-03-17  8:24       ` Jeff King
2009-03-13 16:49 ` Jeff King
2009-03-14  1:27   ` [PATCH] git-push.txt: describe how to default to pushing only current branch Chris Johnsen
2009-03-14 19:26     ` Junio C Hamano
2009-03-14 20:34       ` Jeff King
2009-03-14 20:56         ` Jeff King
2009-03-15  2:49           ` Chris Johnsen
2009-03-15 11:30             ` [PATCH] git-push.txt: describe how to default to pushing only Chris Johnsen
2009-03-17  7:46             ` [PATCH] git-push.txt: describe how to default to pushing only current branch Jeff King
2009-03-14 21:25         ` Junio C Hamano
2009-03-14 21:46           ` Jeff King
2009-03-16  4:51             ` Junio C Hamano
2009-03-15  2:32       ` [PATCH v2] " Chris Johnsen

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=43d8ce650903130537r2459e1d2pef8fffc1c9b3fa5e@mail.gmail.com \
    --to=johnflux@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peter@softwolves.pp.se \
    /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).