From: Junio C Hamano <gitster@pobox.com>
To: "Miles Bader" <miles@gnu.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Include a git-push example for creating a remote branch
Date: Wed, 05 Sep 2007 23:30:31 -0700 [thread overview]
Message-ID: <7v8x7ke260.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <fc339e4a0709052257m4ddc5784obe64a8b75b79b19@mail.gmail.com> (Miles Bader's message of "Thu, 6 Sep 2007 14:57:26 +0900")
"Miles Bader" <miles@gnu.org> writes:
> Maybe I"m weird, but I tend to think of the refs/... syntax as being
> for "only if you're doing something funny" cases.
The "refs/" syntax is there as the lowest level that is
universally usable to create and any ref. It can be used to
push to branches, tags, or even remotes (aka "simulated fetch in
reverse").
It is just nobody felt strong enough reason to sugarcoat the
normalized syntax with something like:
git push --create remote foo v1.2.0
You can be a hero by updating git-push to take such, and make it
interpret as if the user passed the normalized syntax which is:
git push remote foo:refs/heads/foo v1.2.0:refs/tags/v1.2.0
next prev parent reply other threads:[~2007-09-06 6:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 4:44 [PATCH] Include a git-push example for creating a remote branch Shawn O. Pearce
2007-09-06 4:54 ` Miles Bader
2007-09-06 5:01 ` Shawn O. Pearce
2007-09-06 5:57 ` Miles Bader
2007-09-06 6:30 ` Junio C Hamano [this message]
2007-09-06 15:48 ` Carl Worth
2007-09-06 17:42 ` Junio C Hamano
2007-09-06 10:50 ` Wincent Colaiuta
2007-09-06 14:57 ` Kristian Høgsberg
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=7v8x7ke260.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=miles@gnu.org \
--cc=spearce@spearce.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).