Hello,
On 06/12/2010 13:50, Carl Sorensen wrote:
However is it easy to remove the addition to the wrong patch from Rietveld?
Go to the Rietveld issue, and look at the most recent patchset. There's a
link on the upper right corner of the patch set box that says something like
"delete patch set"
I have deleted this because I got myself in a bit of a twist with git cl
and branches.
Sorry for wasting anyone's time. I will repost a new patch (probabuy
tomorrow now).
James
On 06/12/2010 14:04, James wrote:
This for
http://code.google.com/p/lilypond/issues/detail?id=1287
Initial patch
On Mon, Dec 6, 2010 at 2:07 PM, James wrote:
> Ah, I saw Carl's email before yours.
>
> I have reposted a new patch on Rietveld and just need to remove it from the
> 'other' one.
>
> Then I will chase for the former.
>
> If the worst comes to the worst, I don't mind aborting redoing a make
> doc-c
Graham,
On 06/12/2010 13:59, Graham Percival wrote:
On Mon, Dec 6, 2010 at 1:27 PM, James wrote:
I was hoping this would give a new patch not add to the existing.
Finish the existing one first. Wait until it's been pushed. If
necessary, remind people that you're waiting for reviews.
@gra
On 06/12/2010 13:50, Carl Sorensen wrote:
On 06/12/2010 13:44, Carl Sorensen wrote:
>> Create a new branch with the second change, and do git-cl upload from the
>> second branch.
>
> That's a bit beyond me.
>
> :(
Well, let me give you the exact commands:
git branch -f newbranch
git check
This for
http://code.google.com/p/lilypond/issues/detail?id=1287
Initial patch made and uploaded.
http://codereview.appspot.com/3473042
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-dev
On Mon, Dec 6, 2010 at 1:27 PM, James wrote:
> I was hoping this would give a new patch not add to the existing.
Finish the existing one first. Wait until it's been pushed. If
necessary, remind people that you're waiting for reviews.
> @graham (or anyone) can someone help me out with this?
>
>
On 12/6/10 6:46 AM, "James" wrote:
> Hello,
>
> On 06/12/2010 13:44, Carl Sorensen wrote:
>> Create a new branch with the second change, and do git-cl upload from the
>> second branch.
>
> That's a bit beyond me.
>
> :(
Well, let me give you the exact commands:
git branch -f newbranch
git
Hello,
On 06/12/2010 13:44, Carl Sorensen wrote:
Create a new branch with the second change, and do git-cl upload from the
second branch.
That's a bit beyond me.
:(
However is it easy to remove the addition to the wrong patch from Rietveld?
James
_
On 12/6/10 6:27 AM, "James" wrote:
> Hang on.
>
> I have made a mistake with git cl.
>
> I was hoping this would give a new patch not add to the existing.
>
> Sorry.
>
> @graham (or anyone) can someone help me out with this?
Create a new branch with the second change, and do git-cl upload fr
Hang on.
I have made a mistake with git cl.
I was hoping this would give a new patch not add to the existing.
Sorry.
@graham (or anyone) can someone help me out with this?
The two patches are for independent files.
James
On 06/12/2010 13:25, James wrote:
This for
http://code.google.com/
This for
http://code.google.com/p/lilypond/issues/detail?id=1287
Initial patch made and uploaded.
http://codereview.appspot.com/3369041
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-deve
12 matches
Mail list logo
