gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: give us a hand with arch


From: Robert Collins
Subject: Re: [Gnu-arch-users] Re: give us a hand with arch
Date: Sat, 27 Sep 2003 20:24:25 +1000

On Sat, 2003-09-27 at 20:09, Andrea Arcangeli wrote:


I'm not endorsing your arguments re needing this behaviour - just
answering the specific HOWTO...

> 1) the commit has to be strict for the kernel usage.  You simply
> can't pretend that we must allow a regexp to catch statically all the
> junk forever, that's not feasible as I stated in the quote above. I feel
> like you're disappointed that we need this feature but I don't think it's
> fixable by hoping everybody does the right thing. The need for the
> strict commit is exactly to allow people to easily find when they do a
> mistake and they left garbage in the tree: to do the right thing before
> doing a commit.

in {arch}/\=tagging-method:
===
explicit
untagged-source unrecognized
exclude ^(.arch-ids|\{arch\})$
junk ^(,.*)$
precious  
^(\+.*|\.gdbinit|\.#ckpts-lock|=build\.*|=install\.*|CVS|CVS\.adm|RCS|RCSLOG|SCCS|TAGS)$
backup
^.*(~|\.~[0-9]+~|\.bak|\.orig|\.rej|\.original|\.modified|\.reject)$
unrecognized ^(.*\.(o|a|so|core|so(\.[[:digit:]]+)*)|core)$
source ^[_=a-zA-Z0-9].*$
====

Equally, AFAIK, the first line can be "tagline" with no change in
behaviour - other than giving you some option flexability in the future.

Rob

(note that email may have naffed the lines: it's one line per regex.)
((Please, don't ask to not have the regex's there. There are *good*
reasons to have them there, as quoted above. Trust me.))

-- 
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]