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 17:30:22 -0400 [thread overview]
Message-ID: <44552C6E.6090601@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604301303010.5231@g5.osdl.org>
Linus Torvalds wrote:
> If you want to push other branches, you need to do
>
> git push repo branch1 branch2 branch3 ...
>
> or
>
> git push --all repo
>
> where the latter does exactly what it says (use "--tags" instead of
> "--all" to just send all tags).
After experimenting, "--all" does indeed provide most of the features
that rsync provides. A few minor niggles:
1) Doesn't propagate local branch deletions to the remote, like rsync does.
2) git-push "-f" doesn't seem to work, but "--force" does.
3) You still have to provide a $repo argument to 'git pull $repo'.
Would like to list the default remote push URL in
.git/remotes/{somefile} so that I need only to do "git push --all" to
have changes send to any number of remote servers.
4) Propagation of alternatives is unclear (at least in docs). Without
my current pack file pre-sharing and hardlinking, I fear needlessly
uploading vanilla linux-2.6.git changes back to kernel.org, when I do a
push. Currently, pack files are downloaded _once_ from kernel.org to
local, and never re-uploaded.
Regards,
Jeff
prev parent reply other threads:[~2006-04-30 21:30 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
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 [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=44552C6E.6090601@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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