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

[Phil Holmes]

----- Original Message ----- 
From: "Janek Warchol" <address@hidden>
To: "LilyPond Developmet Team" <address@hidden>
Sent: Friday, January 06, 2012 10:42 AM
Subject: unexpected(?) git-cl behaviour, adding strange comments to tracker


> Hi,
>
> 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
> origin/master'.  It asked for message describing patch set, i
> answered, and then it said
>
> 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):
>
> Does this mean that something is set-up wrongly?
> 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...
>
> Did i something wrong or that's how it's supposed to work?  Do i need
> to rebase and squash my work into one commit before each use of
> git-cl?
>
> cheers,
> Janek
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

I believe it tries to guess the issue number from your commit message - so 
if you want it to automatically add an update to the correct issue, you need 
to call it something like "Patch fixing thing, associated with issue 1234". 
Otherwise you just type the issue number in when asked.

--
Phil Holmes