Hi Neil,
If you use the same test branch as your original patch (which is
> associated with a particular issue on Rietveld), you can just apply > the revised patch and upload again (git-cl will ask you for a > description which becomes the title of the new patch set on Rietveld.)
I am not sure I am following, esp. the git-cl part. The state of the test branch right now is simply a clone of the HEAD. I had made some changes, then ran the "upload.py" script to generate the first patch. This was without any commits. Then, I made some corrections, and re-ran "upload.py" again -- this is the revised patch. Sure I can do a diff of the two patches, but how do I get that diff to Rietveld? _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
