Re: unexpected(?) git-cl behaviour, adding strange comments to tracker

[Graham Percival]

On Fri, Jan 06, 2012 at 11:42:32AM +0100, Janek Warchoł wrote:
> i've created a patch (on a separate local branch), committed it and
> uploaded with new git-cl; this created new tracker issue (2175).  i
> did some more changes, committed them and called 'git cl upload
...
> We were not able to associate this patch with a google tracker issue.
> Please enter a valid google tracker issue number (or enter nothing to
> create a new issue):

known problem.  It wouldn't be hard to keep track of this stuff
automatically, but we're not doing that at the moment.

Incidently, this item -- writing/modifying/maintaining python
scripts to aid development -- is my top choice for reward vs.
choice in lilypond at the moment.  A few hours of python work each
week can make every developer's life so much easier.

> Anyway, i answered '2175' and it added a comment to issue 2175
> http://code.google.com/p/lilypond/issues/detail?id=2175#c1 but it
> looks not like what i would expect...

That's exactly correct.
(not ideal, but given the current git-cl python script, that is
correct)

> Do i need to rebase and squash my work into one commit before
> each use of git-cl?

Nope, not necessary.

Cheers,
- Graham