From: Daniel Johnson <computerdruid@gmail.com>
To: Eric Raible <raible@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push <branch-name>
Date: Tue, 5 Oct 2010 18:11:44 -0400 [thread overview]
Message-ID: <201010051811.49211.ComputerDruid@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Tuesday 05 October 2010 16:29:50 you wrote:
> A newbie colleague asked why: "git push <branch>" didn't work.
>
> Although I know that "git push <repo> <branch>" is the correct
> syntax, I think that he has a point. If branch.<branch>.remote
> is defined it seems unambiguous to me.
>
> So I can't see any reason NOT to dwimify
>
> git push <branch>
Isn't that syntax reserved for remotes?
for example:
git push origin
I feel like it would be a bad idea to have these 2 types of invocations
overlap in syntax like that.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-10-05 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 22:11 Daniel Johnson [this message]
2010-10-05 22:28 ` git push <branch-name> Eric Raible
2010-10-06 13:41 ` Sebastian Harl
-- strict thread matches above, loose matches on Subject: below --
2010-10-05 20:29 Eric Raible
2010-10-05 22:35 ` Sverre Rabbelier
2010-10-06 0:52 ` Eric Raible
2010-10-07 10:50 ` Michael J Gruber
2010-10-07 17:41 ` Eric Raible
2010-10-08 6:17 ` Michael J Gruber
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=201010051811.49211.ComputerDruid@gmail.com \
--to=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=raible@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.