From: Andreas Ericsson <ae@op5.se>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org, spearce@spearce.org
Subject: Re: [PATCH] Let users override name of per-directory ignore file
Date: Mon, 22 Oct 2007 13:18:14 +0200 [thread overview]
Message-ID: <471C86F6.6010705@op5.se> (raw)
In-Reply-To: <20071022105029.GB31862@diana.vm.bytemark.co.uk>
Karl Hasselström wrote:
> On 2007-10-15 14:09:32 +0200, Andreas Ericsson wrote:
>
>> When collaborating with projects managed by some other scm, it often
>> makes sense to have git read that other scm's ignore-files. This
>> patch lets git do just that, if the user only tells it the name of
>> the per-directory ignore file by specifying the newly introduced git
>> config option 'core.ignorefile'.
>
>> + For example, setting core.ignorefile to .svnignore in
>> + repos where one interacts with the upstream project repo
>> + using gitlink:git-svn[1] will make a both SVN users and
>> + your own repo ignore the same files.
>
>> + The name of the `.gitignore` file can be changed by setting
>> + the configuration variable 'core.ignorefile'. This is useful
>> + when using git for projects where upstream is using some other
>> + SCM. For example, setting 'core.ignorefile' to `.cvsignore`
>> + will make git ignore the same files CVS would.
>
> I agree with what you're trying to do, but you're ignoring the fact
> that Subversion's ignore patterns (and possibly cvs's too -- I haven't
> checked) are not recursive, while the patterns in .gitignore are
> recursive per default. So using ignore patterns directly from
> Subversion ignores more files under git than the same patterns did
> under Subversion.
>
Yes, I just got bitten by this. The top-level .cvsignore file ignores
Makefile (since it's generated from ./configure), but Makefile exists in
several subdirectories where it's *not* generated, but adding !Makefile
to all those places doesn't sit too well with some of the project
maintainers, and cvs doesn't grok /Makefile to mean "toplevel Makefile"
(and it shouldn't since it has no notion of recursive ignores).
> One possible way to solve that would be to optionally have
> non-recursive per-directory ignore files. I haven't looked at how this
> is implemented, though, so I don't know if it's a good suggestion or
> not.
>
I'll have a look at it. Thanks for the review.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-10-22 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:09 [PATCH] Let users override name of per-directory ignore file Andreas Ericsson
2007-10-22 10:50 ` Karl Hasselström
2007-10-22 11:18 ` Andreas Ericsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-15 12:30 Andreas Ericsson
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=471C86F6.6010705@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=spearce@spearce.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).