Messages in this thread | | | Date | Wed, 30 Jan 2002 07:49:56 -0800 | From | Larry McVoy <> | Subject | Re: A modest proposal -- We need a patch penguin |
| |
On Wed, Jan 30, 2002 at 10:14:49AM +0000, Alan Cox wrote: > Larry - can bitkeeper easily be persuaded to take "messages" back all the way > to the true originator of a change. Ie if a diff gets to Linus he can reject > a given piece of change and without passing messages back down the chain > ensure they get the reply as to why it was rejected, and even if > nobody filled anything in that it was looked at and rejected by xyz at > time/date ?
It's certainly possible and there are changes we could make to make it more useful. Right now, there is no record of a change if it goes and then gets rejected right back out; it's as if you patched and then you did a reverse patch.
The good news is that each change (patch) has an identifier, they look like
awc@bitmover.bitmover.com|ChangeSet|20011230212716|39200
and if we kept a record of those that were rejected, it would be trivial for a developer to track whether his change was in/not seen/rejected. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |