-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fair enough. Just one request then:
Is there already or might there be added a symbolic name for the most recent remote revision on a given branch? So, for instance, if I develop on trunk and I want to submit a patch, I could do: fossil diff --from remote --to current and get a diff of all non-synced changes? Sure, I could just make a new branch, but sometimes when I have very specific changes in mind, I prefer to just make a distinction between my trunk and someone else's. Also, how does Fossil handle the case where your change might exactly implement the patch I submitted? Is it intelligent enough to note that the changes a remote update would apply coincide exactly with how things stand now, or would it throw up a bunch of conflicts? Guess that might be where another branch would come in handy, but it's also a definite advantage of bundles, in that preserving history handles the case of merging up with a remote branch. Thanks. On 02/08/2011 04:58 PM, Stephan Beal wrote: > On Tue, Feb 8, 2011 at 10:51 PM, Richard Hipp <d...@sqlite.org> wrote: > >> fossil diff --from VERSION-WHERE-STARTED --to current >patch.txt >> > > Can fossil-generated diffs be used as input to standard patch programs? > > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1RzLAACgkQIaMjFWMehWJj2QCfb+ddH2rSBPSDGovMl16O87VS G0kAn3Zv3Rz0Fe0fGzWRadMR29awVRk3 =nuB1 -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
