git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git builtin "push"
Date: Sun, 30 Apr 2006 15:58:45 -0400	[thread overview]
Message-ID: <445516F5.1090204@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604292111570.9901@g5.osdl.org>

Linus Torvalds wrote:
> Now, the reason I did it as a built-in is partly because it's yet another 
> step on relying less on shell, but it's actually mostly because I've 
> wanted to be able to push to _multiple_ repositories, and the most obvious 
> and simplest interface for that would seem be to just have a "remotes" 
> file that has multiple URL entries.

Thanks!  This is why I still use rsync, even though everybody and their 
mother tells me "Linus says rsync is deprecated."

Fact is, rsync is still the best to push a _bunch_ of branches, in the 
same tree, all in one command.  In an attempt to get away from rsync, I 
even tried putting multiple git:// entries into .git/remotes/origin, 
then doing "git push" with no args, without success.

Each time I have a non-trivial libata update, I've updated twelve (12) 
branches, and think its highly silly to have to run

	url=git://git.kernel.org/...jgarzik/...
	git push $url $branch:$branch

twelve times.

	Jeff

  parent reply	other threads:[~2006-04-30 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30  4:22 [PATCH] git builtin "push" Linus Torvalds
2006-04-30  7:08 ` Junio C Hamano
     [not found] ` <20060430054049.7856f24c.seanlkml@sympatico.ca>
2006-04-30  9:40   ` sean
2006-04-30 19:58 ` Jeff Garzik [this message]
2006-04-30 20:07   ` Linus Torvalds
     [not found]     ` <20060430165028.215d4fdf.seanlkml@sympatico.ca>
2006-04-30 20:50       ` sean
2006-04-30 21:05         ` Linus Torvalds
2006-04-30 21:47           ` Junio C Hamano
2006-04-30 21:30     ` Jeff Garzik

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=445516F5.1090204@garzik.org \
    --to=jeff@garzik.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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.
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).