git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Abrahams <dave@boostpro.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
	Chris Packham <judge.packham@gmail.com>,
	David Abrahams <dave@boostpro.com>,
	git@vger.kernel.org
Subject: Re: Separate default push/pull?
Date: Thu, 11 Feb 2010 21:32:37 -0500	[thread overview]
Message-ID: <m2iqa3gp4q.wl%dave@boostpro.com> (raw)
In-Reply-To: <7veikrl1m1.fsf@alter.siamese.dyndns.org>

At Thu, 11 Feb 2010 16:49:26 -0800,
Junio C Hamano wrote:
> 
> Jeff King <peff@peff.net> writes:
> 
> > I think what he would need is a "push.defaultRemote" config option,
> > which universally overrides branch.*.remote for pushing.
> 
> Or "branch.*.pushremote".
> 
> But does it really make sense to get changes from one place and send
> changes to somewhere completely unrelated?

It's not unrelated; it's a publicly-readable clone of the source repo
to which I have write permission.  After pushing changes there I send
a pull request to the owner of the source repo.

-- 
Dave Abrahams           Meet me at BoostCon: http://www.boostcon.com
BoostPro Computing
http://www.boostpro.com

      parent reply	other threads:[~2010-02-12  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 16:36 Separate default push/pull? David Abrahams
2010-02-11 18:57 ` Chris Packham
2010-02-12  0:14   ` Jeff King
2010-02-12  0:49     ` Junio C Hamano
2010-02-12  1:05       ` Jeff King
2010-02-12  5:57         ` Junio C Hamano
2010-02-13 11:58           ` Jeff King
2010-02-12  2:32       ` David Abrahams [this message]

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=m2iqa3gp4q.wl%dave@boostpro.com \
    --to=dave@boostpro.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=judge.packham@gmail.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).