On Sun, May 17, 2020 at 10:08 AM Urs Liska wrote:
>
> Am Sonntag, den 17.05.2020, 10:01 +0200 schrieb Han-Wen Nienhuys:
> > On Sun, May 17, 2020 at 9:55 AM Urs Liska
> > wrote:
> > > Hello all,
> > >
> > > although I have admittedly been pretty much silent about all this I
> > > would like to ask
On Sun, May 17, 2020 at 10:08:12AM +0200, Urs Liska wrote:
> Do I understand you correctly that README.txt is generated upon
> compiling LilyPond? So where does it end up, I couldn't find a
> README.txt neither in the source repository nor in the installation
> directory. Does it only end up in the
Am Sonntag, den 17.05.2020, 10:01 +0200 schrieb Han-Wen Nienhuys:
> On Sun, May 17, 2020 at 9:55 AM Urs Liska
> wrote:
> > Hello all,
> >
> > although I have admittedly been pretty much silent about all this I
> > would like to ask about getting access to the LilyPond repository
> > in
> > the ne
On Sun, May 17, 2020 at 9:55 AM Urs Liska wrote:
>
> Hello all,
>
> although I have admittedly been pretty much silent about all this I
> would like to ask about getting access to the LilyPond repository in
> the new place as well. My user name there is urs.liska.
>
> One thing I noted while setti
Hello all,
although I have admittedly been pretty much silent about all this I
would like to ask about getting access to the LilyPond repository in
the new place as well. My user name there is urs.liska.
One thing I noted while setting up my account is that we don't have a
README.md in the root d
> In any case it's not clear to me whether I should prepare for the
> migration today or not. This would be less frustrating if other
> high- volume developers (including but not limited to David,
> Han-Wen, Werner) commented on the plan...
I like it, so please proceed! And thanks for working a
Am Sonntag, den 10.05.2020, 11:59 +0200 schrieb David Kastrup:
> I am running Patchy right now (it's not just this commit but also a few
> by Jonas) but it would make sense if nobody pushed anything afterwards.
Famous last words. In any case, if something gets to the wrong repo or
branch, it's rat
Han-Wen Nienhuys writes:
> On Sun, May 10, 2020 at 11:57 AM David Kastrup wrote:
>
>> output-distance: set device properties in batch driver file
>>
>> This fixes the output quality of the regtest results.
>>
>> Previously, the code sets a device by doing
>>
>> (png16m) finddevi
On Sun, May 10, 2020 at 11:57 AM David Kastrup wrote:
> output-distance: set device properties in batch driver file
>
> This fixes the output quality of the regtest results.
>
> Previously, the code sets a device by doing
>
> (png16m) finddevice
>
> this put a default device
David Kastrup writes:
> Han-Wen Nienhuys writes:
>
>> On Sun, May 10, 2020 at 11:37 AM David Kastrup wrote:
>>>
>>> Han-Wen Nienhuys writes:
>>>
>>> > Sorry. I'm fine with the migration going through today.
>>> >
>>> > We'll all be confused for a few days, but given that gitlab is more
>>> > s
Han-Wen Nienhuys writes:
> On Sun, May 10, 2020 at 11:37 AM David Kastrup wrote:
>>
>> Han-Wen Nienhuys writes:
>>
>> > Sorry. I'm fine with the migration going through today.
>> >
>> > We'll all be confused for a few days, but given that gitlab is more
>> > standard infrastructure than what we
Han-Wen Nienhuys writes:
> On Sun, May 10, 2020 at 11:37 AM David Kastrup wrote:
>>
>> Han-Wen Nienhuys writes:
>>
>> > Sorry. I'm fine with the migration going through today.
>> >
>> > We'll all be confused for a few days, but given that gitlab is more
>> > standard infrastructure than what we
On Sun, May 10, 2020 at 11:37 AM David Kastrup wrote:
>
> Han-Wen Nienhuys writes:
>
> > Sorry. I'm fine with the migration going through today.
> >
> > We'll all be confused for a few days, but given that gitlab is more
> > standard infrastructure than what we have, I think we'll figure it
> > o
Han-Wen Nienhuys writes:
> Sorry. I'm fine with the migration going through today.
>
> We'll all be confused for a few days, but given that gitlab is more
> standard infrastructure than what we have, I think we'll figure it
> out.
>
> I suggest:
>
> * removing write access to issue tracker from m
Le 10/05/2020 à 10:50, Jonas Hahnfeld a écrit :
Am Samstag, den 09.05.2020, 16:11 -0400 schrieb Dan Eble:
On May 9, 2020, at 15:13, David Kastrup wrote:
Carl Sorensen writes:
->CS At any rate, I think that we should have appropriate CG
instructions at the time we make the switch. They don't
Am Sonntag, den 10.05.2020, 11:05 +0200 schrieb Han-Wen Nienhuys:
> On Sun, May 10, 2020 at 10:51 AM Jonas Hahnfeld wrote:
> > In any case it's not clear to me whether I should prepare for the
> > migration today or not. This would be less frustrating if other high-
> > volume developers (includin
Jonas Hahnfeld writes:
> Am Samstag, den 09.05.2020, 16:11 -0400 schrieb Dan Eble:
>> On May 9, 2020, at 15:13, David Kastrup wrote:
>> > Carl Sorensen writes:
>> > > ->CS At any rate, I think that we should have appropriate CG
>> > > instructions at the time we make the switch. They don't hav
On Sun, May 10, 2020 at 10:51 AM Jonas Hahnfeld wrote:
>
> Am Samstag, den 09.05.2020, 16:11 -0400 schrieb Dan Eble:
> > On May 9, 2020, at 15:13, David Kastrup wrote:
> > > Carl Sorensen writes:
> > > > ->CS At any rate, I think that we should have appropriate CG
> > > > instructions at the tim
Am Samstag, den 09.05.2020, 16:11 -0400 schrieb Dan Eble:
> On May 9, 2020, at 15:13, David Kastrup wrote:
> > Carl Sorensen writes:
> > > ->CS At any rate, I think that we should have appropriate CG
> > > instructions at the time we make the switch. They don't have to be
> > > perfect (the CG h
Am Samstag, den 09.05.2020, 21:13 +0200 schrieb David Kastrup:
> Carl Sorensen writes:
> > On 5/9/20, 12:13 PM, "lilypond-devel on behalf of Jonas Hahnfeld"
> > > hah...@hahnjo.de> wrote:
> >
> >
> > So what's the feeling about the migration? go / no-go for tomorrow?
> >
> > ->CS Do we have a
On May 9, 2020, at 15:13, David Kastrup wrote:
> Carl Sorensen writes:
>
>> ->CS At any rate, I think that we should have appropriate CG
>> instructions at the time we make the switch. They don't have to be
>> perfect (the CG has a much lower editing bar than the NR), but they
>> need to be in
Carl Sorensen writes:
> On 5/9/20, 12:13 PM, "lilypond-devel on behalf of Jonas Hahnfeld"
> hah...@hahnjo.de> wrote:
>
>
> So what's the feeling about the migration? go / no-go for tomorrow?
>
> ->CS Do we have a revision to the CG to go with the migration? I
> haven't seen any red flags that
On 5/9/20, 12:13 PM, "lilypond-devel on behalf of Jonas Hahnfeld"
wrote:
So what's the feeling about the migration? go / no-go for tomorrow?
->CS Do we have a revision to the CG to go with the migration? I haven't seen
any red flags that cause me to oppose the migration. I love the idea of
Am Freitag, den 08.05.2020, 19:10 +0100 schrieb James Lowe:
> On 08/05/2020 12:21, Jonas Hahnfeld wrote:
> > Am Freitag, den 08.05.2020, 13:07 +0200 schrieb David Kastrup:
> > > Jonas Hahnfeld writes:
> > >
> > > > 3) The idea is to have the "main" repository at GitLab, next to the
> > > > issues
On 08/05/2020 12:21, Jonas Hahnfeld wrote:
Am Freitag, den 08.05.2020, 13:07 +0200 schrieb David Kastrup:
Jonas Hahnfeld writes:
3) The idea is to have the "main" repository at GitLab, next to the
issues and merge requests. This leads to the question what to do with
Savannah because git is di
Am Freitag, den 08.05.2020, 13:07 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
>
> > 3) The idea is to have the "main" repository at GitLab, next to the
> > issues and merge requests. This leads to the question what to do with
> > Savannah because git is distributed anyway. I first thoug
Jonas Hahnfeld writes:
> 3) The idea is to have the "main" repository at GitLab, next to the
> issues and merge requests. This leads to the question what to do with
> Savannah because git is distributed anyway. I first thought about only
> pushing "important" branches and tags to GitLab (master,
Am Freitag, den 08.05.2020, 11:03 +0200 schrieb Valentin Villenave:
> On 5/8/20, Jonas Hahnfeld wrote:
> > 3) The idea is to have the "main" repository at GitLab, next to the
> > issues and merge requests.
>
> If the two are kept in sync (if and when you enable mirroring), does
> that mean some o
On 5/8/20, Jonas Hahnfeld wrote:
> I haven't heard further objections which, for me, means we are going
> with GitLab. If you don't agree, now's your final time to speak up.
Thanks for tackling this!
> 3) The idea is to have the "main" repository at GitLab, next to the
> issues and merge request
Am Freitag, den 08.05.2020, 10:17 +0200 schrieb Jean-Charles
Malahieude:
> Le 08/05/2020 à 08:57, Jonas Hahnfeld a écrit :
> > I haven't heard further objections which, for me, means we are going
> > with GitLab. If you don't agree, now's your final time to speak up.
> > Otherwise I would like to t
Le 08/05/2020 à 08:57, Jonas Hahnfeld a écrit :
I haven't heard further objections which, for me, means we are going
with GitLab. If you don't agree, now's your final time to speak up.
Otherwise I would like to tackle the migration rather soon to take
advantage of the new opportunities :-)
This
I haven't heard further objections which, for me, means we are going
with GitLab. If you don't agree, now's your final time to speak up.
Otherwise I would like to tackle the migration rather soon to take
advantage of the new opportunities :-)
This leads me to some final considerations:
1) I'm goin
32 matches
Mail list logo
