From: Steffen Prohaska <prohaska@zib.de>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git push (mis ?)behavior
Date: Fri, 28 Sep 2007 11:26:25 +0200 [thread overview]
Message-ID: <09A90525-8B0B-4249-904C-722BCC544B4E@zib.de> (raw)
In-Reply-To: <20070928065823.GB19299@artemis.corp>
On Sep 28, 2007, at 8:58 AM, Pierre Habouzit wrote:
> On Fri, Sep 28, 2007 at 06:52:47AM +0000, Steffen Prohaska wrote:
>>
>> On Sep 27, 2007, at 9:22 PM, Junio C Hamano wrote:
>>
>>>
>>> So what's the desired semantics?
>>>
>>> The current semantics is:
>>>
>>> "git push" says "you do not say to which repository?" and
>>> consults "branch.<current>.remote" but defaults to 'origin'
>>> if unconfigured.
>>>
>>> "git push <name>" (or using the <name> determined as above)
>>> says "you do not say which branches?" and consults
>>> "remote.<name>.push" to find branches to push out, but
>>> defaults to 'matching branches' if unconfigured.
>>>
>>> What you would want to change is the fallback behaviour for
>>> unconfigured "remote.<name>.push". I think it is sensible to
>>> have an option to make it push only the current branch.
>>
>> I'm not sure that changing the fallback behaviour for unconfigured
>> "remote.<name>.push" is sufficient.
>>
>> When "remote.<name>.push" is set I'd expect "git push" to
>> choose only the 'right' remote.<name>.push lines, that is
>> the lines that have the current branch as the local ref.
>> "git push" would only push the current branch, which could be pushed
>> to 0 or more branches on the remote side. If no "remote.<name>.push"
>> contains the current branch as a local ref nothing would happen
>> (maybe a warning?). If several "remote.<name>.push" have the current
>> branch as the local ref the branch would be pushed to several
>> remote branches. But other branches than the current branch
>> would _never_ be pushed if no argument is given to 'git push'.
>
> I'm not really sure that it makes sense, as by default, git push
> won't
> create a new remote ref. So unless you have a branch that matches some
> remote ref, but that you never want to push, even when on it and
> typing
> git push... there is nothing that could happen by mistake.
>
> So if you don't want to push such a branch, ever, then you should
> IMHO
> not name it in a way that it matches a refspec in the first place, and
> be safe.
I could have a couple of local branches typically pushed to a couple of
remote branches. "git push origin" would update all remote refs.
But I may also be interested to push only the current branch I'm working
on. I may also have some pending fixes on another branch that should not
be pushed now. Currently I need to do "git push origin
<current>:<someremote>".
Let me put it as a question: How can I push changes from the current
branch to all remote refs it is configured to push to via
"remote.<name>.push"
without pushing anything else at the same time?
Steffen
next prev parent reply other threads:[~2007-09-28 9:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:04 git push (mis ?)behavior Pierre Habouzit
2007-09-27 13:30 ` Wincent Colaiuta
2007-09-27 15:28 ` Benoit SIGOURE
2007-09-27 19:22 ` Junio C Hamano
2007-09-27 19:36 ` Pierre Habouzit
2007-09-28 6:52 ` Steffen Prohaska
2007-09-28 6:58 ` Pierre Habouzit
2007-09-28 9:26 ` Steffen Prohaska [this message]
2007-09-28 9:44 ` Junio C Hamano
2007-09-28 10:04 ` Steffen Prohaska
2007-09-28 7:07 ` Junio C Hamano
2007-09-28 9:11 ` Steffen Prohaska
2007-09-28 13:31 ` Johannes Schindelin
2007-10-09 5:05 ` Jan Hudec
2007-10-09 7:23 ` Steffen Prohaska
2007-09-28 12:38 ` Wincent Colaiuta
2007-10-03 5:10 ` Miles Bader
2007-10-03 5:39 ` Junio C Hamano
2007-10-03 6:47 ` Wincent Colaiuta
2007-10-03 8:32 ` Miles Bader
2007-10-03 7:35 ` Pierre Habouzit
2007-10-03 8:57 ` Miles Bader
2007-10-03 9:03 ` Pierre Habouzit
2007-10-03 10:25 ` Wincent Colaiuta
2007-10-03 10:49 ` Karl Hasselström
2007-10-03 11:08 ` Junio C Hamano
2007-10-03 11:22 ` Wincent Colaiuta
2007-10-03 13:14 ` Karl Hasselström
2007-10-03 15:27 ` Johannes Schindelin
2007-10-03 16:07 ` Karl Hasselström
2007-10-03 16:18 ` Johannes Schindelin
2007-10-03 16:28 ` Pierre Habouzit
2007-10-03 16:44 ` Johannes Schindelin
2007-10-03 17:02 ` Karl Hasselström
2007-10-04 14:47 ` Steffen Prohaska
2007-10-04 15:54 ` Wincent Colaiuta
2007-10-04 16:24 ` Steffen Prohaska
2007-10-04 17:49 ` Wincent Colaiuta
2007-10-03 16:26 ` Wincent Colaiuta
2007-10-03 11:10 ` Benoit SIGOURE
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09A90525-8B0B-4249-904C-722BCC544B4E@zib.de \
--to=prohaska@zib.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).