2012/12/2 David Kastrup :
> Thomas Morley writes:
>
>> 2012/12/2 David Kastrup :
>>> Thomas Morley writes:
>>>
2012/12/2 David Kastrup :
> David Kastrup writes:
>
>> Do
>>
>> git pull -r
>>
>> first to get your patch up-to-date.
>
> To get your git-cl rep
Thomas Morley writes:
> 2012/12/2 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2012/12/2 David Kastrup :
David Kastrup writes:
> Do
>
> git pull -r
>
> first to get your patch up-to-date.
To get your git-cl repository up-to-date, sorry.
>>>
>>> Tried t
2012/12/2 David Kastrup :
> Thomas Morley writes:
>
>> 2012/12/2 David Kastrup :
>>> David Kastrup writes:
>>>
Do
git pull -r
first to get your patch up-to-date.
>>>
>>> To get your git-cl repository up-to-date, sorry.
>>>
>>> --
>>> David Kastrup
>>>
>>>
>>>
Thomas Morley writes:
> 2012/12/2 David Kastrup :
>> David Kastrup writes:
>>
>>> Do
>>>
>>> git pull -r
>>>
>>> first to get your patch up-to-date.
>>
>> To get your git-cl repository up-to-date, sorry.
>>
>> --
>> David Kastrup
>>
>>
>> ___
>> lilypo
2012/12/2 David Kastrup :
> David Kastrup writes:
>
>> Do
>>
>> git pull -r
>>
>> first to get your patch up-to-date.
>
> To get your git-cl repository up-to-date, sorry.
>
> --
> David Kastrup
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu
David Kastrup writes:
> Do
>
> git pull -r
>
> first to get your patch up-to-date.
To get your git-cl repository up-to-date, sorry.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilyp
Thomas Morley writes:
> 2012/12/2 Thomas Morley :
>> 2012/12/2 Reinhold Kainhofer :
>>> On 2012-12-02 12:50, Thomas Morley wrote:
Trying to upload a new patch set for issue 2966, I ran into said
git-cl-issue.
Using LilyDev, I tried to apply Reinholds patch (after storing it in
Thomas Morley writes:
> Trying to upload a new patch set for issue 2966, I ran into said git-cl-issue.
> Using LilyDev, I tried to apply Reinholds patch (after storing it in
> git-cl.diff), but the terminal returns:
>
> harm@harm-laptop ~/lilypond-git (dev/local_working)$ git apply git-cl.diff
>
2012/12/2 Thomas Morley :
> 2012/12/2 Reinhold Kainhofer :
>> On 2012-12-02 12:50, Thomas Morley wrote:
>>>
>>> Trying to upload a new patch set for issue 2966, I ran into said
>>> git-cl-issue.
>>> Using LilyDev, I tried to apply Reinholds patch (after storing it in
>>> git-cl.diff), but the termi
2012/12/2 Reinhold Kainhofer :
> On 2012-12-02 12:50, Thomas Morley wrote:
>>
>> Trying to upload a new patch set for issue 2966, I ran into said
>> git-cl-issue.
>> Using LilyDev, I tried to apply Reinholds patch (after storing it in
>> git-cl.diff), but the terminal returns:
>>
>> harm@harm-lapto
On 2012-12-02 12:50, Thomas Morley wrote:
Trying to upload a new patch set for issue 2966, I ran into said git-cl-issue.
Using LilyDev, I tried to apply Reinholds patch (after storing it in
git-cl.diff), but the terminal returns:
harm@harm-laptop ~/lilypond-git (dev/local_working)$ git apply git
2012/12/2 David Kastrup :
> James writes:
>
>> David,
>>
>> On 2 December 2012 08:55, David Kastrup wrote:
>>> James writes:
>>>
>> ...
>>> Well, I have been using it already, and it is clearly an improvement
>>> over the previous situation, so it should be committed to git-cl, and
>>> people sh
James writes:
> David,
>
> On 2 December 2012 08:55, David Kastrup wrote:
>> James writes:
>>
> ...
>> Well, I have been using it already, and it is clearly an improvement
>> over the previous situation, so it should be committed to git-cl, and
>> people should be encouraged to update their ver
David,
On 2 December 2012 08:55, David Kastrup wrote:
> James writes:
>
...
> Well, I have been using it already, and it is clearly an improvement
> over the previous situation, so it should be committed to git-cl, and
> people should be encouraged to update their version of git-cl afterwards
>
James writes:
> Hello,
>
> On 1 December 2012 17:24, Reinhold Kainhofer
> wrote:
>> On 2012-12-01 17:12, David Kastrup wrote:> My interpretation is that Google
>> has set codereview.appspot.com so that
>>> any http request will automatically get redirected to https, and git-cl
>>> is unable to
James wrote Sunday, December 02, 2012 8:15 AM
>
> On 1 December 2012 17:24, Reinhold Kainhofer
> wrote:
>> On 2012-12-01 17:12, David Kastrup wrote:> My interpretation is that Google
>> has set codereview.appspot.com so that
>>> any http request will automatically get redirected to https, and g
Hello,
On 1 December 2012 17:24, Reinhold Kainhofer wrote:
> On 2012-12-01 17:12, David Kastrup wrote:> My interpretation is that Google
> has set codereview.appspot.com so that
>> any http request will automatically get redirected to https, and git-cl
>> is unable to deal with that.
>
> Well, gi
Reinhold Kainhofer wrote Saturday, December 01, 2012 5:24 PM
> On 2012-12-01 17:12, David Kastrup wrote
:> My interpretation is that Google has set codereview.appspot.com so that
> > any http request will automatically get redirected to https, and git-cl
> > is unable to deal with that.
>
> It's
On 2012-12-01 17:12, David Kastrup wrote:> My interpretation is that
Google has set codereview.appspot.com so that
> any http request will automatically get redirected to https, and git-cl
> is unable to deal with that.
Well, git-cl (I would prefer git-cly to indicate this is not the
standard g
19 matches
Mail list logo
