-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/03/2013 05:12 PM, Richard Hipp wrote:
> Might that be a useful approach for Fossil, too? > > >> If I understand you correctly, I believe this is what happens if you do >> your lots of tiny commits into a --private branch, then merge that >> private branch into trunk (or some other public branch) at the end. >> When you push to another repo, on the other repo that does not contain >> the private branch, the merge looks like a single commit that contains >> all of the changes all mashed together into one big change. Yep; that hides all the private branch history into the private repo, though - what I'm talking about *looks* like that but has the history available to everyone if you "expand" the commit by clicking on a [+] in the web UI or some such. ABS - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDqsj8ACgkQRgz/WHNxCGo76ACdF0rjW4NqXpNFSR8Z4gdItTHF m/MAn2nj/pIFIXaAuSYbL5m+DHO2LpSs =bGDp -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
