git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Brad Larson <bklarson@gmail.com>, git@vger.kernel.org
Subject: Re: .git as file pointing to directory?
Date: Fri, 05 Nov 2010 00:28:20 +0100	[thread overview]
Message-ID: <4CD34194.8010002@web.de> (raw)
In-Reply-To: <vpqbp64d9e0.fsf@bauges.imag.fr>

Am 04.11.2010 23:14, schrieb Matthieu Moy:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
> 
>> Am 04.11.2010 19:32, schrieb Matthieu Moy:
>>> Brad Larson <bklarson@gmail.com> writes:
>>>
>>>> Sorry if this is obvious, I can't figure out what term to search for.
>>>>
>>>> At gittogether there was some talk about having .git be a file, not a
>>>> folder, with contents pointing to the real .git directory.  Similar to
>>>> a symlink, but supported in Windows.  Is there a specific name for
>>>> this feature?  Where can I find more details?  Which version of git
>>>> introduced this?
>>>
>>> It has been discussed under the name "gitlink", which was
>>> unfortunately also used for something else in the subtree
>>> implementation, but AFAIK, it has never been implemented.
>>
>> Hmm, AFAIK gitlinks are already in heavy use for submodule entries ...
> 
> Err, isn't that precisely what I was saying? The same word has been
> used in the subtree implementation, but the other concept with the
> same name hasn't been implemented.

Sorry, seems like I misunderstood what you where saying.

  reply	other threads:[~2010-11-04 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 18:22 .git as file pointing to directory? Brad Larson
2010-11-04 18:32 ` Matthieu Moy
2010-11-04 20:35   ` Jens Lehmann
2010-11-04 22:14     ` Matthieu Moy
2010-11-04 23:28       ` Jens Lehmann [this message]
2010-11-04 18:43 ` Jonathan Nieder
2010-11-04 21:07   ` Brad Larson

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=4CD34194.8010002@web.de \
    --to=jens.lehmann@web.de \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=bklarson@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).