From: Junio C Hamano <gitster@pobox.com>
To: martin f krafft <madduck@madduck.net>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: ignoring non-submodule subrepositories
Date: Thu, 27 Sep 2007 12:29:15 -0700 [thread overview]
Message-ID: <7vy7eructw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070927170700.GA10250@lapse.madduck.net> (martin f. krafft's message of "Thu, 27 Sep 2007 18:07:00 +0100")
martin f krafft <madduck@madduck.net> writes:
> I have a repository inside another, and for several reasons, I do
> not want to use git-submodule in this case. My issue is that
> git-status lists the subrepository as untracked.
>
> Of course, I could add it to .gitignore alright, but instead
> I wonder whether it would not make sense to ignore subdirectories
> themselves containing .git/ directories, not explicitly so as to not
> mess with git-submodule, but implicitly.
>
> Thoughts?
I've had a line "/Meta" in my .git/info/excludes ever since I
started to maintain the 'todo' branch (which is managed in an
independent repository situated there, and pushed into the
'todo' branch of git.git), and having to have that line never
bothered me.
While I do not think of a reason offhand not to ignore anything
that has .git/ and is not a subproject, other than that ignoring
might interfere your adding such a separate project as a
subproject. I know "git add" would countermand the ignore list,
but not listing means it lets you forget.
Thinking about it more, such a separate project is not even
special. We list untracked files to remind you that you might
want to add them. Why should a separate project that is not
tracked by us (i.e. a potential superproject) be treated any
differently from other untracked things on the filesystem?
So, my thoughts are moderate "negative" at this point, but
others may have better arguments..
prev parent reply other threads:[~2007-09-27 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 17:07 ignoring non-submodule subrepositories martin f krafft
2007-09-27 19:29 ` Junio C Hamano [this message]
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=7vy7eructw.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.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 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).