2015-08-23 18:58 GMT+02:00 James Lowe <p...@gnu.org>: > Hello, > > ***Important do please read*** > > Google Tracker will be 'read-only' on the 25th August. At the moment, > as I understand it we are still 'transitioning' to a new tracker > system for issues but Rietveld is still working as normal. > > This will make keeping track of patches a bit more involved for me to > keep track of current/in progress changes as well as making sure that > I know which patches need (re)testing. > > There were some suggestions about sending git formatted patches to > 'bug' but as they are all going to probably end up at my feet (so to > speak) I am proposing the following. > > After today (August 24th onwards) can we do the following please: > > > 1. For NEW patches (as well as those patches that have had updates, > and so need RETESTING) I'd prefer if they were uploaded to Rietveld as > normal first and then the *URL* to Rietveld issue emailed to me > instead of the git formatted patch. This makes sure that if a patch is > 'lost' or 'missed' or 'forgotten' then we still have the Rietveld > issue to fall back on and at the same time we don't clog the dev list > up with patch files of different dates versions. > > Put an appropriate string in the subject of the email sent to me like > 'PATCH TO TEST' or 'PATCH UPDATED' or something obvious like that and > I'll hopefully do the rest. > > Try to use p...@gnu.org email address rather than my gmail account - > I'll monitor both but keeping things in one place is simpler for me.
You mean a private mail, iiuc. [...] > NEW: > > Dan Eble: Group #include directives at top of file > http://code.google.com/p/lilypond/issues/detail?id=4560 > > Thomas Morley: input/regression/bookparts.ly fails at PDF conversion stage > http://code.google.com/p/lilypond/issues/detail?id=4554 This one is on push. You likely meant: Thomas Morley: Clear fret-diagram- and harp-pedal-input-strings from whitespace http://code.google.com/p/lilypond/issues/detail?id=4575 Thanks a lot for all your great work, Harm _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
