Phil Holmes wrote Friday, July 13, 2012 5:56 PM
> From: "Thomas Morley" <thomasmorle...@googlemail.com> > >> What should I do? > > Run the command > > git cl issue 6352049 > > and then repeat > > git cl upload > > git cl needs to be told the issue number on Rietveld, if it's different from > the most recent. Or use a fresh git branch for the patch. The Rietveld number is associated with the local git branch. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
