git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Eric Raible <raible@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git push <branch-name>
Date: Thu, 07 Oct 2010 12:50:11 +0200	[thread overview]
Message-ID: <4CADA5E3.5060405@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTi=k9aEqpvoEvU5f-t-63==fouFmJ+OxO=6sQd89@mail.gmail.com>

Eric Raible venit, vidit, dixit 06.10.2010 02:52:
> On Tue, Oct 5, 2010 at 3:35 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> Since it is such a simple command expansion, why not create an alias
>> that does just that?
> 
> Because I don't want an alias, I want to extend git-push.
> 
> According to the man page, "git push"
> 
> "Works like git push <remote>, where <remote> is the current branch's remote
>  (or origin, if no remote is configured for the current branch)."
> 
> What I'm advocating is that "git push <branch>" would be described with:
> 
> "Works like git push <remote> <branch>, where <remote> is the <branch>'s remote
>  (or origin, if no remote is configured for <branch>)."

Now, if I have a remote foo and a branch foo, what is

git push foo

supposed to do?

Michael

  reply	other threads:[~2010-10-07 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 20:29 git push <branch-name> Eric Raible
2010-10-05 22:35 ` Sverre Rabbelier
2010-10-06  0:52   ` Eric Raible
2010-10-07 10:50     ` Michael J Gruber [this message]
2010-10-07 17:41       ` Eric Raible
2010-10-08  6:17         ` Michael J Gruber
  -- strict thread matches above, loose matches on Subject: below --
2010-10-05 22:11 Daniel Johnson
2010-10-05 22:28 ` Eric Raible
2010-10-06 13:41   ` Sebastian Harl

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=4CADA5E3.5060405@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=raible@gmail.com \
    --cc=srabbelier@gmail.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. 
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).