Reviewers: Trevor Daniels,
https://codereview.appspot.com/6948070/diff/1/Documentation/contributor.texi
File Documentation/contributor.texi (right):
https://codereview.appspot.com/6948070/diff/1/Documentation/contributor.texi#newcode74
Documentation/contributor.texi:74: @verbatiminclude ly-gram
2012/12/24 Thomas Morley :
> Hi,
>
> trying
>
> ~/lilypond-git (dev/local_working)$ git pull -r
>
> returns:
>
> fatal: read error: Connection reset by peer
>
> What's wrong?
>
>
>
> -Harm
After rebooting LilyDev, it works again.
-Harm
___
lilypond-dev
>> It is just wires sticking out, and it is wires to something that
>> was never intended to be shorted.
>
> Let the wires stick out and let people experiment! Us, users, et
> cetera. That is, in my opinion, the best way for things to move
> forward. What I'm interested in fixing are the bleed
Hi,
trying
~/lilypond-git (dev/local_working)$ git pull -r
returns:
fatal: read error: Connection reset by peer
What's wrong?
-Harm
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Mon, Dec 24, 2012 at 7:22 AM, m...@mikesolomon.org
wrote:
> On 24 déc. 2012, at 10:36, d...@gnu.org wrote:
>
> On 2012/12/24 07:28:17, mike7 wrote:
>
> On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
>
>
>> All of this is absolutely devastatingly horrible code that is not
>> reconcilable
On 24 déc. 2012, at 10:36, d...@gnu.org wrote:
> On 2012/12/24 07:28:17, mike7 wrote:
>
>> On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
>
>> > All of this is absolutely devastatingly horrible code that is not
>> > reconcilable with sane per-session semantics and tampers with
> LilyPond
On 24 déc. 2012, at 10:10, m...@hohlart.de wrote:
> On 2012/12/24 07:28:17, mike7 wrote:
>
>> So what I need from you, if you're willing to help me out, are
> explanations of
>> how this causes bleedover effects.
>
> IIRC, the functions define-session and define-session-public were
> created fo
On 2012/12/24 07:28:17, mike7 wrote:
So what I need from you, if you're willing to help me out, are
explanations of
how this causes bleedover effects.
IIRC, the functions define-session and define-session-public were
created for that very reason, so perhaps they are what you're after?
Just
On 2012/12/24 08:10:25, marc wrote:
On 2012/12/24 07:28:17, mike7 wrote:
> So what I need from you, if you're willing to help me out, are
explanations of
> how this causes bleedover effects.
IIRC, the functions define-session and define-session-public were
created for that very reason, so
On 2012/12/24 07:28:17, mike7 wrote:
On 24 déc. 2012, at 01:10, mailto:d...@gnu.org wrote:
> All of this is absolutely devastatingly horrible code that is not
> reconcilable with sane per-session semantics and tampers with
LilyPond
> internals in a way that has bleed-over effects into futur
10 matches
Mail list logo