From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: Multiple remote.<...>.fetch and .push patterns
Date: Tue, 01 Jul 2008 11:00:54 +0200 [thread overview]
Message-ID: <g4croa$3eu$1@ger.gmane.org> (raw)
In-Reply-To: <308083c30806301252l25f072anafbc457f48c6b19e@mail.gmail.com>
Adr3nal D0S venit, vidit, dixit 30.06.2008 21:52:
> In reference to my question about .git/remotes/ko, Jon Loeliger
> <jdl@freescale.com> wrote:
>
>> You can have both Push: and Pull: lines for a remote there.
>>
>> Or have I misunderstood your question here?
>
> I know that I can create files in .git/remotes that look like Linus'
> ko sample. But I was wondering if this could be done with git-config.
> I have some developers that are new to SCMs in general and git in
> particular. They are a little nervous playing in the git directory.
>
> Also, I was uncertain how settings in .git/remotes files interact with
> git-config ...fetch and ...push settings, if at all.
The files under remotes are the old way of configuring remotes (see git
help push). The new are config lines in the remotes section, as written
by "git remote". I don't think "git remote" can write the lines you
want, so I'd suggest:
git config remote.ko.url kernel.org:/pub/scm/git/git.git
git config remote.ko.fetch refs/heads/master:refs/tags/ko-master
git config --add remote.ko.fetch refs/heads/next:refs/tags/ko-next
git config --add remote.ko.fetch refs/heads/maint:refs/tags/ko-maint
You can add similar lines for push with the key remote.ko.push. Note
that you have to use "--add" if you want to have multiple lines for the
same key in config. Also, you can add a "+" in front of the refspec, but
I'm a bit surprised you want that on pushing to ko.
Cheers,
Michael
next prev parent reply other threads:[~2008-07-01 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 18:58 Multiple remote.<...>.fetch and .push patterns Adr3nal D0S
2008-06-30 19:29 ` Jon Loeliger
2008-06-30 19:52 ` Adr3nal D0S
2008-07-01 9:00 ` Michael J Gruber [this message]
2008-07-01 9:27 ` Junio C Hamano
2008-07-01 9:59 ` Michael J Gruber
2008-07-01 13:04 ` 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='g4croa$3eu$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail.fm \
--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).