From: "Adr3nal D0S" <adr3nald0s@gmail.com>
To: git@vger.kernel.org
Subject: Multiple remote.<...>.fetch and .push patterns
Date: Mon, 30 Jun 2008 13:58:49 -0500 [thread overview]
Message-ID: <308083c30806301158i1100c84dqe7f50daad417934c@mail.gmail.com> (raw)
How can I do something like what is shown in Everyday git using git-config?
$ cat .git/remotes/ko
URL: kernel.org:/pub/scm/git/git.git
Pull: master:refs/tags/ko-master
Pull: next:refs/tags/ko-next
Pull: maint:refs/tags/ko-maint
Push: master
Push: next
Push: +pu
Push: maint
I know I can do:
git config remote.ko.fetch refs/heads/*:refs/tags/ko-*
but that will get all KO heads. And I have no clue about the push version.
next reply other threads:[~2008-06-30 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 18:58 Adr3nal D0S [this message]
2008-06-30 19:29 ` Multiple remote.<...>.fetch and .push patterns Jon Loeliger
2008-06-30 19:52 ` Adr3nal D0S
2008-07-01 9:00 ` Michael J Gruber
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=308083c30806301158i1100c84dqe7f50daad417934c@mail.gmail.com \
--to=adr3nald0s@gmail.com \
--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).