From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Anjib Mulepati <anjibcs@hotmail.com>
Subject: Re: Push from specific directory.
Date: Thu, 22 Mar 2012 19:09:51 -0500 [thread overview]
Message-ID: <4F6BBF4F.9080302@gmail.com> (raw)
In-Reply-To: <7vlimsur95.fsf@alter.siamese.dyndns.org>
On 3/22/2012 6:53 PM, Junio C Hamano wrote:
> Neal Kreitzinger<nkreitzinger@gmail.com> writes:
>
>> See this thread for the "cons" of nested git repos: (I don't think
>> there are any "pros".)
>> http://thread.gmane.org/gmane.comp.version-control.git/190372
>
> Hmph, I see you saying "I will keep this in mind" and "Thanks" at the end,
> and back then I took it that you understood why/how nested working trees
> are useful. Perhaps you didn't and I misunderstood you?
I neglected to distinguish between ignored-nested-git-repos (has pros)
and tracked-subdir-nested-git-repos (has no pros) in my preface to the
thread link. That was an oversight on my part.
BTW, I'm am still being compelled to deal with
tracked-subdir-nested-git-repos and I have not found any pros to them so
your original assessment of that technique still stands. ;-)
v/r,
neal
next prev parent reply other threads:[~2012-03-23 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 22:04 Push from specific directory Anjib Mulepati
2012-03-22 22:57 ` Jeff King
2012-03-22 23:22 ` Neal Kreitzinger
2012-03-22 23:27 ` Jeff King
2012-03-22 23:56 ` Neal Kreitzinger
2012-03-22 23:53 ` Junio C Hamano
2012-03-23 0:09 ` Neal Kreitzinger [this message]
2012-03-23 1:29 ` Neal Kreitzinger
[not found] ` <BLU0-SMTP315865C5026D08E76594E5DB1460@phx.gbl>
2012-03-23 15:30 ` Neal Kreitzinger
2012-03-26 14:27 ` Holger Hellmuth
2012-03-26 14:41 ` Neal Kreitzinger
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=4F6BBF4F.9080302@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=anjibcs@hotmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.