git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sean <seanlkml@sympatico.ca>
To: Linus Torvalds <torvalds@osdl.org>
Cc: jeff@garzik.org, junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] git builtin "push"
Date: Sun, 30 Apr 2006 16:50:28 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP037751CEC096DA29400513AEB00@CEZ.ICE> (raw)
Message-ID: <20060430165028.215d4fdf.seanlkml@sympatico.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0604301303010.5231@g5.osdl.org>

On Sun, 30 Apr 2006 13:07:42 -0700 (PDT)
Linus Torvalds <torvalds@osdl.org> wrote:

> The way it works is that
> 
> 	"git push repo"
> 
> with no branch specs will update all branches that are IN COMMON between 
> your tree and the repository you're pushing to. In other words, it's meant 
> to sync up the branches that you have already pushed.

True, as long as you don't have any Push: lines in your .git/remotes/repo
file.  Any such lines act just like you gave them on the command line
which afaik effectively removes the ability to say "update all branches
we have in common".

Sean

  reply	other threads:[~2006-04-30 20:55 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 [this message]
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=BAYC1-PASMTP037751CEC096DA29400513AEB00@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=git@vger.kernel.org \
    --cc=jeff@garzik.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).