From: Andreas Schwab <schwab@linux-m68k.org>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Creating own hierarchies under $GITDIR/refs ?
Date: Sun, 02 Feb 2014 12:04:18 +0100 [thread overview]
Message-ID: <m2mwi9rd1p.fsf@linux-m68k.org> (raw)
In-Reply-To: <87a9e92424.fsf@fencepost.gnu.org> (David Kastrup's message of "Sun, 02 Feb 2014 11:37:39 +0100")
David Kastrup <dak@gnu.org> writes:
> Are there some measures one can take/configure in the parent repository
> such that (named or all) additional directories inside of $GITDIR/refs
> would get cloned along with the rest?
$ git config --add remote.orgin.fetch '+refs/notes/*:refs/notes/*'
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2014-02-03 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 10:37 Creating own hierarchies under $GITDIR/refs ? David Kastrup
2014-02-02 11:00 ` Duy Nguyen
2014-02-02 11:19 ` David Kastrup
2014-02-02 11:31 ` John Keeping
2014-02-02 11:42 ` David Kastrup
2014-02-02 12:24 ` John Keeping
2014-02-02 23:44 ` Jed Brown
2014-02-02 12:00 ` Duy Nguyen
2014-02-02 12:09 ` David Kastrup
2014-02-02 11:04 ` Andreas Schwab [this message]
2014-02-02 23:26 ` Jeff King
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=m2mwi9rd1p.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=dak@gnu.org \
--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).