From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] gitfs pre-release 0.04
Date: Mon, 4 Dec 2006 12:03:49 -0800 [thread overview]
Message-ID: <20061204200349.GX47959@gaz.sfgoth.com> (raw)
In-Reply-To: <el1tg0$n07$1@sea.gmane.org>
Jakub Narebski wrote:
> Not true. Symlink HEAD still works, and we have even core.preferSymlinkRefs
> configuration variable.
Yes, but it has to be a symlink pointing into "refs/", not just a regular
file holding a hash value. Which is fine for most purposes but sort of a
pain for me.
I'll probably have it be a symlink to "refs/gitfs-dynamic" or something and
then have "refs" be populated with that synthetic file and symlinks to
any of the normal contents of the refs directory. Not too bad, but will
take a little bit of code.
next prev parent reply other threads:[~2006-12-04 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:40 [ANNOUNCE] gitfs pre-release 0.04 Mitchell Blank Jr
2006-12-04 19:40 ` Jakub Narebski
2006-12-04 20:03 ` Mitchell Blank Jr [this message]
2006-12-04 19:54 ` 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=20061204200349.GX47959@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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