From: David Mansfield <david@cobite.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Junio C Hamano <junkio@cox.net>,
Brian Gerst <bgerst@didntduck.org>,
git@vger.kernel.org
Subject: Re: [PATCH Cogito] cg-init breaks if . contains sub-dir
Date: Tue, 10 May 2005 17:31:11 -0400 [thread overview]
Message-ID: <4281281F.6000101@cobite.com> (raw)
In-Reply-To: <20050510095825.GI11221@kiste.smurf.noris.de>
Matthias Urlichs wrote:
> Hi,
>
> Jan-Benedict Glaw:
>
>>>Please don't change that without talking to Linus.
>>
>>I won't. You haven't seen a patch from me "fixing" this, too. *I*
>>consider this as a defect, but that doesn't mean that I'll force others
>>to take this view, too. But maybe I'll talk Linus into this when he's
>>back from his trip.
>
>
> That would be a good idea; I do support dropping (or at least relaxing)
> that rule. For excluding unwanted files, I'd suggest using a .git/ignore
> file with nice shiny patterns (*.a *.o *.swp ...) inside -- git already
> supports that anyway.
>
Speaking of which, for a large project, (such as the kernel) it is a
pain in the butt if exclude lists only consider the 'basename' of the
file, and cannot include any path matching information.
For a long time there were generated files in the kernel which had the
same names as non-generated files somewhere else in the kernel tree
(under a different path). Making an automated 'take latest patch from
Linus, apply, commit' was really a pain because of this.
Is there/will there be support for path matching in the ignore files?
If the answer is no, but people like the idea, I could look into it.
David
next prev parent reply other threads:[~2005-05-10 21:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 23:39 [PATCH Cogito] cg-init breaks if . contains sub-dir Brandon Philips
2005-05-10 1:36 ` Morten Welinder
2005-05-10 3:41 ` Matthias Urlichs
2005-05-10 5:17 ` Brian Gerst
2005-05-10 7:52 ` Jan-Benedict Glaw
2005-05-10 8:04 ` Jan-Benedict Glaw
2005-05-10 8:36 ` Matthias Urlichs
2005-05-10 8:56 ` Martin Waitz
2005-05-10 8:56 ` Jan-Benedict Glaw
2005-05-10 9:47 ` David Greaves
2005-05-10 8:42 ` David Greaves
2005-05-10 9:01 ` Junio C Hamano
2005-05-10 9:32 ` Jan-Benedict Glaw
2005-05-10 9:39 ` Matthias Urlichs
2005-05-10 9:45 ` Jan-Benedict Glaw
2005-05-10 9:58 ` Matthias Urlichs
2005-05-10 21:31 ` David Mansfield [this message]
2005-05-11 5:25 ` [PATCH Cogito] match pathnames in exclude handling Matthias Urlichs
2005-05-11 21:30 ` H. Peter Anvin
2005-05-12 7:54 ` Matthias Urlichs
2005-05-10 15:14 ` [PATCH Cogito] cg-init breaks if . contains sub-dir H. Peter Anvin
2005-05-12 18:53 ` Petr Baudis
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=4281281F.6000101@cobite.com \
--to=david@cobite.com \
--cc=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--cc=jbglaw@lug-owl.de \
--cc=junkio@cox.net \
--cc=smurf@smurf.noris.de \
/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.