[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ignored 'core' directory
From: |
Spiro Trikaliotis |
Subject: |
Re: ignored 'core' directory |
Date: |
Tue, 11 May 2004 09:51:30 +0200 |
User-agent: |
Mutt/1.5.6i |
Hello,
* On Mon, May 10, 2004 at 03:52:15PM -0400 Larry Jones wrote:
> Spiro Trikaliotis writes:
> >
> > I don't think this is enough. There are circumstances where one wants to
> > import files named core, or files named .old, .bak or the like.
>
> That's what -I! is for.
Yes, I know. Actually, I myself directed the OP to the corresponding
part of TFM.
> > The best thing is to document it in a way the user can find it easily -
> > that's why I want this link added to the documentation - and let the
> > user decide for himself what to do.
>
> Agreed.
Especially since it took me some hours to sport that part of the
documentation.
> > OTOH, I can't think of an occasion where it would make sense to ignore
> > files on import. That is, if we want to change the behaviour, why not
> > have a -I ! as default argument for ignore?
>
> Because you usually *don't* want to import executables, zip files, etc.
> into your *source* control system.
Yes, but if I import a source tarball - obviously, the most common usage
of an import - the are usually no executables in there. But I have had
more than one project where a source file or source directory was named
'core'.
Another thought: Since people or surprised especially on import,
wouldn't it be nice to warn the user whenever a file or directory is
ignored? This way, the user at least is informed that something went
wrong.
Best regards,
Spiro.
--
Spiro R. Trikaliotis I'm subscribed to the mailing lists I'm posting,
http://www.trikaliotis.net/ so please refrain from Cc:ing me. Thank you.