From: Junio C Hamano <junkio@cox.net>
Date: Sun, 30 Apr 2006 07:08:34 GMT
Subject: Re: [PATCH] git builtin "push"
Message-ID: <7vwtd7zgjx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0604292111570.9901@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

> Junio - I currently have a "push-all" script in each of the repos I 
> maintain. That has worked, but I'd just rather do something like
>
> 	git push all
>
> instead, and have it pick up the list of URI's from .git/remotes/all.

Makes sense.  I am still somewhat drunk (cachaça -- agua de
beber -- pretty good but strong stuff), so I will look at the
patch tomorrow, but...

> How do you do multi-targeted pushes?

I do not.  At least not that often.  I merge things up, test all
of "master", "maint", "next", and "pu" locally (the Meta/Doit
script, available after checking out "todo" branch in Meta/
subdirectory), then "git push ko-private" to push into ~/git of
the kernel.org machine and do "all branches" test again
(Meta/DoKernelOrg script).  Only after all that passes, I do a
"git push ko" from my local machine to push into the public
area, /pub/scm/git/git.git, of the kernel.org machine.

For Solaris and Cygwin testing, only occasionally, I do not push
but pull from the machines at work.  This is because I want to
catch breakage of pull side myself if there is one.

The only time I do multi-target push is just before cutting a
release.  In addition to "git push ko-private" to push into the
primary Opteron machine, I push to "git push ko-old-private" to
push into the i386 machine at kernel.org, "Meta/DoKernelOrg
master" (or "maint") to prepare RPMs for i386 there, and another
"Meta/DoKernelOrg master" (or "maint") on the Opteron to
prepare RPMs for x86-64.  So personally I never felt the need
for a multi-target push.