Re: [RFD] Explicitly documenting patch submission

Thomas Gleixner
2004-05-24T21:25:34Z

On Monday 24 May 2004 23:05, Linus Torvalds wrote:
> On the other hand, I'd rather have the process be "we always have the
> sign-off", coupled with just plain common sense.

Makes sense

> So I'd rather encourage people to sign off on even the silly stuff, than
> to have to constantly make a judgement call. At the same time, I think
> that if somebody _didn't_ sign off on the simple stuff, we shouldn't just
> run around in circles like hens in a hen-house, we should just say "hey,
> we've got brains, the process isn't meant to be _stupid_".

:)

One more practical point.

Module maintainers receive patches from various hackers and commit them after
review with the appropriate "sign-offs" to a subsystem repository.

Subsystem maintainer makes his monthly / whatever upstream update.

Until now he just reviews the total changes from his last update til now. To
keep your proposed procedure consistent he would be forced now to go through
the "trusted" step by step commitments of his module maintainers, extract the
"sign-offs" and add his own "sign-off" to each single step before pushing the
improvements upstream.

IMHO it would suffice for this situation, if the "sign-offs" are tracked in
the subsystem repository and the subsystem maintainer signs off for the
overall patch / contribution which is sent upstream.

--
Thomas
________________________________________________________________________
Steve Ballmer quotes the statistic that IT pros spend 70 percent of their
time managing existing systems. That couldn’t have anything to do with
the fact that 99 percent of these systems run Windows, could it?
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de