[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fix mordents and pralltriller in articulate.ly (issue 5784084)
From: |
Graham Percival |
Subject: |
Re: Fix mordents and pralltriller in articulate.ly (issue 5784084) |
Date: |
Thu, 15 Mar 2012 04:10:12 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Mar 15, 2012 at 02:49:29PM +1100, Peter Chubb wrote:
> >>>>> "graham" == graham <address@hidden> writes:
>
> graham> ok. In the future, when updating a patch, please point git-cl
> graham> at your existing issue (which was orginally 2404, but I'm
> graham> going to close 2404 and 2405 and leave 2406).
>
> Can I do that in .git/config?
Unfortunately not.
> It currently points at a Rietveld issue 5784084
> --- I wasn't aware that there was a separate Lilypond issue number
> name space. Is git-cl meant to print out the new Lilypond issue number?
git-cl will say "I can't find an issue number"; at that point,
manually type in 2406.
Hopefully somebody will add code.google-issue-number-tracking to
git-cl at some point, but that's not likely to happen soon.
> I think the (begin is unnecessary too. I was a real novice scheme
> programmer when I wrote all this --- still am. The body of a let
> clause is already a list of fucntion calls.
Well, each patch will need to go through the review. You could
let the current ones go through, then do more edits; or you could
cancel the current one, make more edits, then send a single patch
through.
- Graham