From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pierre Habouzit <madcoder@debian.org>
Cc: "Karl Hasselström" <kha@treskal.com>,
"Wincent Colaiuta" <win@wincent.com>,
"Miles Bader" <miles@gnu.org>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: git push (mis ?)behavior
Date: Wed, 3 Oct 2007 17:44:39 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710031742400.28395@racer.site> (raw)
In-Reply-To: <20071003162816.GA17403@artemis.corp>
Hi,
On Wed, 3 Oct 2007, Pierre Habouzit wrote:
> On Wed, Oct 03, 2007 at 04:18:56PM +0000, Johannes Schindelin wrote:
> > This thread is getting painful. Lot's of "I want"s, but nobody to date
> > came up with a solution that makes both oldtimers and newtimers happy.
>
> I think I made a proposal that tries to reach some kind of consensus:
>
> `git push`::
> no arguments given just pushes the current branch you're on, into
> origin, if a refspec matches.
I use that sometimes, and I do not want only the current branch to be
pushed.
> `git push <remote>`::
> works like now (aka pushes all branches that match a remote branch
> in the given remote).
That would make things inconsistent, and inconsistent things are always
hard to explain.
> This way, you can have current "git push" using "git push origin", but
> you also have a convenient way to push only the current branch into your
> default remote repository without needing to spell out:
>
> $ git push origin `git symbolic-ref HEAD`
I wonder how hard it would be to teach _everybody_ to specify _exactly_
what they want.
Of course, we'd need an "--existing" option to git-push to trigger the
behaviour that we have right now.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-03 16:46 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
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 [this message]
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=Pine.LNX.4.64.0710031742400.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kha@treskal.com \
--cc=madcoder@debian.org \
--cc=miles@gnu.org \
--cc=win@wincent.com \
/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).