git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, Git List <git@vger.kernel.org>
Subject: Re: git submodule vs GIT_WORK_TREE
Date: Fri, 29 Jun 2012 13:23:54 -0700	[thread overview]
Message-ID: <7v4npt50kl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7v8vf551iu.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 29 Jun 2012 13:03:21 -0700")

Junio C Hamano <gitster@pobox.com> writes:

>>> Declaring that a checked out submodule _must_ have its controlling
>>> repository as ".git" at its root level, i.e. it should be accessible
>>> without using GIT_WORK_TREE/GIT_DIR at all just like a normal Git
>>> repository is, would be a clean way to avoid the issue altogether
>>> and it still will allow the top-level superproject to be structured
>>> in a funny way to require GIT_WORK_TREE/GIT_DIR to access it,
>>
>> I fear this would make vcsh unable to support submodules, ever.
>
> Then think of a workable alternative.  As it stands, I would have to
> say that what vcsh tries to do with git is broken with respect to
> submodules.

Just to avoid misunderstanding.  I didn't mean "vcsh and vcsh alone
is broken while other solutions work just fine".  What I meant was
"I agree with you that what vcsh tries to do is unworkable".

  reply	other threads:[~2012-06-29 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 12:28 git submodule vs GIT_WORK_TREE Richard Hartmann
2012-06-26 16:07 ` Junio C Hamano
2012-06-26 18:27   ` Jens Lehmann
2012-06-26 19:51     ` Junio C Hamano
2012-06-26 22:30       ` Jens Lehmann
2012-06-26 22:53         ` Junio C Hamano
2012-06-29  8:43           ` Richard Hartmann
2012-06-29 20:03             ` Junio C Hamano
2012-06-29 20:23               ` Junio C Hamano [this message]
2012-06-29 21:03               ` Junio C Hamano
2012-07-01 10:34                 ` Richard Hartmann
2012-07-02  8:22                   ` Junio C Hamano
2012-06-29  9:10     ` Richard Hartmann

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=7v4npt50kl.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=richih.mailinglist@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;
as well as URLs for NNTP newsgroup(s).