From: Miles Bader <miles@gnu.org>
To: git@vger.kernel.org
Subject: Re: Not pushing all branches?
Date: Sat, 14 Mar 2009 10:08:20 +0900 [thread overview]
Message-ID: <874oxwgbcr.fsf@catnip.gol.com> (raw)
In-Reply-To: 7v4oxxgpil.fsf@gitster.siamese.dyndns.org
Junio C Hamano <gitster@pobox.com> writes:
> - The first "-" one; even though it may be useful to be able to say
> "the remote the current branch is associated with by default", using
> "-" as a short-hand for that might be harmful to the long term UI
> health, and further study was requested, which hasn't been responded
> yet.
I've often wished for such a thing in some contexts, actually...
e.g., "git diff REMOTE_BRANCH" to see what updates are pending if I
merge... Also, it would be nice to have a more concise way to say
"git merge REMOTE_BRANCH".
I'm not sure "-" seems like the best syntax though... maybe it's a bit
_too_ short.
[Is there a general standard syntax for "keywords" in git, e.g., to
distinguish them from branch/rev names? I mean, if the standard syntax
were "@foo", then one could imagine "git diff @remote" or something.]
-miles
--
Run away! Run away!
next prev parent reply other threads:[~2009-03-14 1:10 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
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 [this message]
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=874oxwgbcr.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.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.
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).