I'm not sure that I have understood all the git/quilt obskure usages here.
But I have the following question: Why is it necessary to rebuild
linux-next on a daily basis? I understand that it is build on a bunch of
special purpose trees. But after aggregating all this, can't we make a
diff to last day linux-next and take this patch to check in a new
linux-next??? This way all linux-next would be based on each other...
Posted Jul 10, 2008 14:48 UTC (Thu) by bfields (subscriber, #19510)
[Link]
"can't we make a diff to last day linux-next and take this patch to check in a new
linux-next???"
The resulting diff would represent all the work done by all maintainers in a day. It would be
large, and not very logical.
If I have a conflict with something in linux-next, then I want to be able to identify exactly
the smallest logical change that produces the conflict, and who did it (in case I need to ask
them about it). It would be difficult to do that if a single change that's checked in is a
big agglomerations of unrelated stuff by lots of different developers.