From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Michael Schubert <mschub@elegosoft.com>,
Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Proposal: branch.<name>.remotepush
Date: Thu, 7 Feb 2013 15:30:17 -0800 [thread overview]
Message-ID: <20130207233017.GD19397@google.com> (raw)
In-Reply-To: <CALkWK0=53riU3xKbKkyAVS8--9VoAU5P6h88MQ9-geW=H5+a-w@mail.gmail.com>
Hi Ram,
Ramkumar Ramachandra wrote:
> And yes, a regular `git push origin refs/for/master` is just retarded.
The usual incantation is "git push gerrit HEAD:refs/for/master". Is
the code review creation push that uses a different branchname from
the branch the integrator pulls what seems backward, or is it the need
to specify a refname at all on the command line?
I agree that a "[branch "master"] pushremote" configuration would be
handy. pushremote instead of remotepush to be less surprising to
people who have already seen pushurl.
Good luck,
Jonathan
next prev parent reply other threads:[~2013-02-07 23:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:14 Proposal: branch.<name>.remotepush Ramkumar Ramachandra
2013-02-07 17:45 ` Michael Schubert
2013-02-07 19:37 ` Ramkumar Ramachandra
2013-02-07 19:49 ` Ramkumar Ramachandra
2013-02-07 20:14 ` Ramkumar Ramachandra
2013-02-07 23:30 ` Jonathan Nieder [this message]
2013-02-07 23:41 ` Junio C Hamano
2013-02-08 7:48 ` Jonathan Nieder
2013-02-08 8:16 ` Junio C Hamano
2013-02-08 10:38 ` Michael J Gruber
2013-02-08 17:11 ` Junio C Hamano
2013-02-08 17:16 ` Junio C Hamano
2013-02-08 18:29 ` Ramkumar Ramachandra
2013-02-08 19:13 ` Junio C Hamano
2013-02-08 18:36 ` Jonathan Nieder
2013-02-08 18:42 ` Ramkumar Ramachandra
2013-02-08 19:18 ` Junio C Hamano
2013-02-09 7:29 ` Ramkumar Ramachandra
2013-02-08 4:48 ` Jeff King
2013-02-08 6:08 ` Junio C Hamano
2013-02-08 6:28 ` Jeff King
2013-02-08 6:45 ` Junio C Hamano
2013-02-08 9:22 ` Jeff King
2013-02-08 17:06 ` Junio C Hamano
2013-02-08 18:03 ` Ramkumar Ramachandra
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=20130207233017.GD19397@google.com \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mschub@elegosoft.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).