git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "MichaelTiloDressel@t-online.de" <MichaelTiloDressel@t-online.de>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: cogito remote branch
Date: Mon, 12 Nov 2007 11:47:52 +0100	[thread overview]
Message-ID: <1IrWpc-0kFExM0@fwd28.aul.t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0711120954460.4362@racer.site>


Johannes Schindelin wrote:

>> A push is needed somewhere in order to prevent every remote to be
pushed 
>> by default, right?

>You mean a "push" config variable?  No.  I think I mentioned in my
first 
>reply that

>	git push  <remote> <branch>...

>works quite wonderfully.

I mean a push = .. line in the [remote <name>] block.
And if there is such a line than git-push without arguments will push
only
the current branch. For me that is nice, because if I forgot to give 
an argument to git-push it will not push other branches.

If there is no such line all the remotes (that don't have a push line?) 
get pushed. 

Cheers,
Michael

  reply	other threads:[~2007-11-12 10:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 13:08 (unknown) Michael Dressel
2007-11-11 15:22 ` (no subject) Johannes Schindelin
2007-11-12  8:00   ` cogito remote branch MichaelTiloDressel
2007-11-12  9:55     ` Johannes Schindelin
2007-11-12 10:47       ` MichaelTiloDressel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-11 13:11 Michael Dressel
2007-11-10 12:35 Michael Dressel
2007-11-09 13:16 MichaelTiloDressel
2007-11-09 13:20 ` Andreas Ericsson
2007-11-09 13:51   ` MichaelTiloDressel
2007-11-09 14:17     ` Johannes Schindelin
2007-11-09 16:10       ` MichaelTiloDressel
2007-11-09 16:28         ` Jon Loeliger
2007-11-10 11:27           ` Michael Dressel
2007-11-10 11:52             ` Jakub Narebski

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=1IrWpc-0kFExM0@fwd28.aul.t-online.de \
    --to=michaeltilodressel@t-online.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.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).