From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Anjib Mulepati <anjibcs@hotmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Push from specific directory.
Date: Thu, 22 Mar 2012 18:56:29 -0500 [thread overview]
Message-ID: <4F6BBC2D.10204@gmail.com> (raw)
In-Reply-To: <20120322232723.GA15676@sigill.intra.peff.net>
On 3/22/2012 6:27 PM, Jeff King wrote:
> On Thu, Mar 22, 2012 at 06:22:13PM -0500, Neal Kreitzinger wrote:
>
>>> You have a repository inside a repository. So when you are in (c),
>>> you will be pushing the commits from (c), not from (a). I'm not
>>> really sure what you are trying to accomplish with that.
>>>
>> 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
>
> Nested git repos are OK. I use one inside my git.git checkout to hold
> meta-information and scripts (and I know Junio does the same thing). But
> I mark the sub-repository as ignored in the parent repository. What's
> insane is trying to track the same set of files from two different
> repositories. And I think that is the confusing case in the thread you
> mentioned.
>
Yes, hopefully the nested git repo is ignored by the higher level git
repo. However, if it was ignored I don't suspect one would be wondering
if it was ok to "only" push from the nested repo. I could be wrong.
v/r,
neal
next prev parent reply other threads:[~2012-03-22 23:56 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 [this message]
2012-03-22 23:53 ` Junio C Hamano
2012-03-23 0:09 ` Neal Kreitzinger
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=4F6BBC2D.10204@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=anjibcs@hotmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.