From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Michael Schubert <mschub@elegosoft.com>,
Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: Proposal: branch.<name>.remotepush
Date: Fri, 08 Feb 2013 09:11:28 -0800 [thread overview]
Message-ID: <7vsj563f3z.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5114D5B0.5080906@drmicha.warpmail.net> (Michael J. Gruber's message of "Fri, 08 Feb 2013 11:38:40 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> As for the triangle remote, I really think we should clean up the
> situation regarding push, pushurlinsteadof and the various different and
> inconclusive output formats of "git remote" (with or without "-v", with
> or without a remote name) first, before introducing yet another way to
> twist things around. "git push downstream" does not hurt any kittens
> (while git remote ouput does, somehwat).
As people tend to fetch more often than they push if they are
working on a real project where the others as a whole will be far
more productive than any single individual, I agree that keeping
"git fetch" (or "git pull") lazy by having "origin" point at where
they fetch from and be a bit more explicit in "git push" would
actually make sense.
next prev parent reply other threads:[~2013-02-08 17:11 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
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 [this message]
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=7vsj563f3z.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mschub@elegosoft.com \
--cc=peff@peff.net \
/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).