git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Michael Dressel <MichaelTiloDressel@t-online.de>
Cc: git@vger.kernel.org
Subject: Re: (no subject)
Date: Sun, 11 Nov 2007 15:22:56 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711111520260.4362@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0711111359590.9401@castor.milkiway.cos>

Hi,

On Sun, 11 Nov 2007, Michael Dressel wrote:

> 
> >Michael Dressel wrote:
> >Ok nice. Another thing is that git-push will push all the tracking 
> >branches in refs/remotes/origin. 
> 
> I learned that I only have to edit the .git/config file to avoid that 
> git-push pushes everything. 

It is documented that you can use "git push origin <branchname>".

> [remote "origin1"]
>         url = /home/repo/src
>         fetch = +refs/heads/master:refs/remotes/origin/master
>         push = +refs/heads/master:refs/heads/master

With "push", it is not necessary to specify the ":<target>".

Also, if "master" is unambiguous, you can write just "master" instead of 
"refs/heads/master".

Furthermore, I suggest not forcing (that's  what "+" does) the push, since 
it is quite possible that you push something old in the wrong direction.  

Hth,
Dscho

  reply	other threads:[~2007-11-11 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 13:08 (unknown) Michael Dressel
2007-11-11 15:22 ` Johannes Schindelin [this message]
2007-11-12  8:00   ` cogito remote branch MichaelTiloDressel
2007-11-12  9:55     ` Johannes Schindelin
2007-11-12 10:47       ` MichaelTiloDressel
  -- strict thread matches above, loose matches on Subject: below --
2025-02-12 14:07 (No Subject) blg666
2024-03-06 12:36 Emilis Kiškis
2008-07-12 22:31 (no subject) Kevin Phair
2008-04-21 18:21 George Shammas
2007-07-17 22:39 Mark Levedahl
2005-06-20  7:08 dierbro
2005-04-18 16:31 Davide Rossetti

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=Pine.LNX.4.64.0711111520260.4362@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=MichaelTiloDressel@t-online.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).