git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	David Lee <davidomundo@gmail.com>,
	git@vger.kernel.org
Subject: Re: Separate default remotes for pulling and pushing
Date: Tue, 10 May 2011 08:47:53 -0400	[thread overview]
Message-ID: <BANLkTimUn9e=5CfDcvQdgNYY4_pqbi8peQ@mail.gmail.com> (raw)
In-Reply-To: <20110509220459.GA3719@sigill.intra.peff.net>

On Mon, May 9, 2011 at 6:04 PM, Jeff King <peff@peff.net> wrote:
> I think it is important to note that calling them both "origin" is
> definitely the wrong thing. The proposal is instead that "git push"
> without a remote would default to something besides "origin". For people
> who publish multiple places, it might even make sense for it to be an
> iterative push to each place.

While developing in a particular repo, I constantly have to push to
two compile machines. I just dropped a Makefile into the top of my
working tree:

all: push
amend:
	git amend -a
	git --no-pager diff @{1}
	make push
push:
	make -j 2 mac win
mac:
	git push mac
win:
	git push win

j.

  parent reply	other threads:[~2011-05-10 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07  8:10 Separate default remotes for pulling and pushing David Lee
2011-05-07  9:50 ` Sverre Rabbelier
2011-05-09  8:17   ` Jeff King
2011-05-09  8:34     ` David Lee
2011-05-09 11:10       ` Jeff King
2011-05-09 19:01         ` David Lee
2011-05-09 22:06           ` Jeff King
2011-05-09 16:45     ` Junio C Hamano
2011-05-09 22:04       ` Jeff King
2011-05-09 22:46         ` Junio C Hamano
2011-05-10 20:17           ` Jeff King
2011-05-10 12:47         ` Jay Soffian [this message]
2011-05-10 20:20           ` Jeff King
2011-05-10 21:12             ` Jay Soffian

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='BANLkTimUn9e=5CfDcvQdgNYY4_pqbi8peQ@mail.gmail.com' \
    --to=jaysoffian@gmail.com \
    --cc=davidomundo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=srabbelier@gmail.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).