----- 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. And, again, can we leave this until *AFTER* the CPU? > Andrew. > > -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222
