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

[Miles Bader]

Robert Collins <address@hidden> writes:
> > 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.

I thought of an even better idea: pass the changeset commit computes as
a parameter, e.g., ARCH_CHANGESET=,,commit.changeset.mumble-foo

Then a pre-commit hook has several choices; if ARCH_LIMIT is set, and it
wants to do some testing, it can do a `get' (or a tree copy or whatever)
and then apply the changet...

-miles
-- 
In New York, most people don't have cars, so if you want to kill a person, you
have to take the subway to their house.  And sometimes on the way, the train
is delayed and you get impatient, so you have to kill someone on the subway.
  [George Carlin]