[Top][All Lists]

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

[Gnu-arch-users] Re: fixing and extending "selected commit"

From: Robert Collins
Subject: [Gnu-arch-users] Re: fixing and extending "selected commit"
Date: Fri, 03 Oct 2003 15:41:59 +1000

On Fri, 2003-10-03 at 15:34, Miles Bader wrote:
> Robert Collins <address@hidden> writes:
> > > By modifying the changeset creation mechanism to have the notion of a
> > > `limit', and ignore files not inside it.  Simple and straight-forward
> > > (indeed, I'd think this was the _obvious_ way to do it...).
> > 
> > the nasty problem is interaction with hooks, and nearly any user-policy
> > stuff.
> Why is it a nasty problem?  You can pass any limit as arg to hooks too,
> and let them do what they will (how does it work now, anyway, with the
> current simple restricted commits?).  I guess something like ARCH_LIMIT,
> containing a newline-separated list of the limit args originally passed.

Well there *aren't* pre-commit hooks today, so it's irrelevant.

But Eric's example hook, for pre-commit policy checking, will in many
cases need a full tree 'snapshot' of what is going to be committed.


GPG key available at: <>.

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

reply via email to

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