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 09:00:50 +0100 [thread overview]
Message-ID: <1IrUDz-01jF4a0@fwd29.aul.t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0711111520260.4362@racer.site>
(I forgot to put the subject previously)
> Johannes Schindelin wrote:
>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 ".
>> [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 ":".
So just a line like
push = master
A push is needed somewhere in order to prevent every remote to be pushed
by default,
right?
>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.
O.k. I will reconsider this.
Cheers,
Michael
next prev parent reply other threads:[~2007-11-12 8:01 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 ` MichaelTiloDressel [this message]
2007-11-12 9:55 ` cogito remote branch Johannes Schindelin
2007-11-12 10:47 ` MichaelTiloDressel
-- 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=1IrUDz-01jF4a0@fwd29.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).