On 21/07/16 15:46, Andrew Hughes wrote: > > > ----- Original Message ----- >> On 11/07/16 16:33, Andrew Hughes wrote: >> >>>>> On 11/07/16 15:28, Andrew Hughes wrote: >>>>> I don't really want to lose all the history with just one huge >>>>> patch either. >>>> >>>> In practice, from merging in ports, that is by far the best thing >>>> to do. The history can be found in the development tree. >>> >>> That's certainly not my experience. Having the history available >>> on the working tree has proved invaluable on several occasions. >> >> I'm sure, but it makes an awful mess of the history of the tree >> being merged into. No. > > It means when I'm backporting patches, I can actually tell what > the changes are and why they were made, rather than just pointing > back to one mega-patch.
I'm aware of the disadvantages. However, it's more important that the whole port be reviewable as a single patch. > And, again, can we leave this until *AFTER* the CPU? Yes. Andrew.
