Carl Sorensen wrote Monday, May 04, 2015 4:48 AM
> In searching around on Savannah's page, I found InDefero
> http://www.indefero.net/ which claims to be an open-source lightweight
> copy of Google Code. Unfortunately, it doesn't appear that there are any
> publicly available hosting sites using
Dan Eble writes:
> On May 3, 2015, at 16:42 , David Kastrup wrote:
>>
>> Dan Eble writes:
>>
>>> Adding a wrapper context will have undesirable effects.
>>
>> The question is what requirements or mechanisms we could employ in order
>> to remove the undesirable effects.
>>
>> For example, it
k-ohara5...@oco.net writes:
On 2015/05/03 20:25:22, dak wrote:
On 2015/05/03 16:42:02, Trevor Daniels wrote:
I find it awkward when \absolute c'' and \absolute g'' mean exactly
the same
thing. But it's not like I could not live with it. But I still
would
recommend
just using c to kee
Carl Sorensen writes:
> On 5/3/15 8:33 AM, "Joseph Rushton Wakeling"
> wrote:
>
>>On 10/04/15 09:34, Werner LEMBERG wrote:
>>> So the question is whether Launchpad has a usable API, right? Joseph,
>>> do you know more?c
>>
>>Just to follow up on this, I exchanged a few messages on Reddit with
>
David Kastrup wrote Monday, May 04, 2015 11:30 AM
> Anyone evaluated/tested/whatever Kallithea?
> https://kallithea-scm.org/>. It seems aligned to the Software
> Freedom Convervancy, so maybe we could get Savannah to support it if it
> does the job.
Kallithea doesn't seem to have a native issue
"Trevor Daniels" writes:
> David Kastrup wrote Monday, May 04, 2015 11:30 AM
>
>> Anyone evaluated/tested/whatever Kallithea?
>> https://kallithea-scm.org/>. It seems aligned to the Software
>> Freedom Convervancy, so maybe we could get Savannah to support it if it
>> does the job.
>
> Kallithea
Reviewers: dak, Trevor Daniels, J_lowe,
Message:
Please review
Description:
Docstring and index entries added
Please review this at https://codereview.appspot.com/232180043/
Affected files (+4, -0 lines):
M Documentation/notation/ancient.itely
M ly/property-init.ly
Index: Documentation/n
On 5/3/15 9:48 PM, "Carl Sorensen" wrote:
>
>In searching around on Savannah's page, I found InDefero
>http://www.indefero.net/ which claims to be an open-source lightweight
>copy of Google Code. Unfortunately, it doesn't appear that there are any
>publicly available hosting sites using it, so
Reviewers: J_lowe,
Message:
I've pushed to staging branch.
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=f758afb1497e9d95e564844363f23efa5a313321
Description:
Fix lilypond-invoke-editor's temp dir
To use environment variable TMP and TEMP is
Windows-only conventions.
The POSIX c
2015-05-04 14:46 GMT+02:00 Carl Sorensen :
> More hunting around on Savannah led me to Apache Allura, which is claimed
> to be an open-source (Apache license) follow-on to the
> proprietary-software SourceForge.
>
> It uses git, has webhooks (
> https://forge-allura.apache.org/p/allura/wiki/Webhoo
As promised, a starter list of requirements for the issue handling system,
to allow us to check potential replacements to Google code.
1. Allow creation of a new sequentially numbered issue, with
text describing the issue’s title and details
2. Allow tagging the issue with a range of
Federico Bruni wrote Monday, May 04, 2015 2:53 PM
> Interesting!
> https://forge-allura.apache.org/p/allura/wiki/Features/
>
> I think that the main alternatives are Launchpad (Affero GPL) and Apache
> Allura (Apache License).
> Launchpad provides also the hosting, while Allura should be deploye
"Trevor Daniels" writes:
> Federico Bruni wrote Monday, May 04, 2015 2:53 PM
>
>> Interesting!
>> https://forge-allura.apache.org/p/allura/wiki/Features/
>>
>> I think that the main alternatives are Launchpad (Affero GPL) and Apache
>> Allura (Apache License).
>> Launchpad provides also the host
Sorry if this raises old stuff again.
For me many of your requirwments could be rather easily (and partially
automatically ) be handled with an integrated system of code, review and
issues, i.e. a system that provides something like pull requests.
In addition to many of your list items this woul
Hi Paul, thanks for the suggestions.
As Debian Jessie was released few days ago, I was thinking about a new
LilyDev.
I think I'll first upgrade to a more recent version of live-build and then
add the modifications you are suggesting.
2015-05-04 0:09 GMT+02:00 Paul Morris :
> A. Suggestions for L
David Kastrup wrote Monday, May 04, 2015 5:21 PM
> Wasn't Savannah's main system Savane a fork of SourceForge's proprietary
> software version? Anybody have more of a clue about the relations
> between the various versions and what that might mean for our chances of
> getting this system adopted
2015-05-04 18:32 GMT+02:00 Federico Bruni :
> As Debian Jessie was released few days ago, I was thinking about a new
> LilyDev.
> I think I'll first upgrade to a more recent version of live-build and then
> add the modifications you are suggesting.
>
I have a question: does anybody use LilyDev as
"Trevor Daniels" writes:
> David Kastrup wrote Monday, May 04, 2015 5:21 PM
>
>> Wasn't Savannah's main system Savane a fork of SourceForge's proprietary
>> software version? Anybody have more of a clue about the relations
>> between the various versions and what that might mean for our chances
- Original Message -
From: "Federico Bruni"
To: "Paul Morris"
Cc: "LilyPond Development Team"
Sent: Monday, May 04, 2015 6:19 PM
Subject: Re: Improving the Contributors Guide and LilyDev
2015-05-04 18:32 GMT+02:00 Federico Bruni :
As Debian Jessie was released few days ago, I was
On 5/4/15 11:19 AM, "Federico Bruni" wrote:
>So I'd rather put a script to download the repository when the user logs
>in
>for the first time.
>What do you think?
Isn't that the way it works right now? If not, it certainly should.
There should be a script that configures git properly (i.e. with
On 5/4/15 10:21 AM, "David Kastrup" wrote:
>
>Wasn't Savannah's main system Savane a fork of SourceForge's proprietary
>software version? Anybody have more of a clue about the relations
>between the various versions and what that might mean for our chances of
>getting this system adopted by Sava
On 5/4/15 10:16 AM, "Trevor Daniels" wrote:
>Ah, wait .. sourceforce have an importer from GoogleCode. I had to
>register to see it, but that's easy. After that, it's here
>
>https://sourceforge.net/p/import_project/google-code/
>
>It says it will import Wiki pages, source code (SVN, Git or Hg),
Carl Sorensen writes:
> On 5/4/15 10:21 AM, "David Kastrup" wrote:
>
>>If we have a really viable migration path out of non-Savannah hosting,
>>it seems like putting our eggs not in too many outsourced baskets
>>might save us from some future headaches like the Google code one.
>
> I'm not sure
Carl Sorensen
> I'm fine if we can get everything on Savannah, but it seems
> to me that in the past, there was a feeling that Savane's
> bug tracking was significantly inferior to Google Code.
> I don't know, because I never used it.
Just as a reminder, we had a very helpful interchange with
On 5/4/15 1:16 PM, "Trevor Daniels" wrote:
>
>Carl Sorensen
>
>> I'm fine if we can get everything on Savannah, but it seems
>> to me that in the past, there was a feeling that Savane's
>> bug tracking was significantly inferior to Google Code.
>> I don't know, because I never used it.
>
>Just
Carl Sorensen wrote Monday, May 04, 2015 8:40 PM
> So perhaps it would be a good idea to test Allura
> on SourceForge, and see if we like it. If we do,
> then we could let the Savannah people know, and
> maybe they'd be willing to use it as their issue tracker.
OK, I've created a project on Sou
On 04/05/15 22:01, Trevor Daniels wrote:
>
> You can see the progress here:
> https://sourceforge.net/p/testlilyissues/tickets/
I'm getting
Error 403
Read access required
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu
On 04/05/15 04:02, Carl Sorensen wrote:
>> 2. Compiling with LilyDev (2.3) and Compiling (4.x)
> 2.3 is about getting it set up with LilyDev. 4.x is about general work
> whether with or without LilyDev. We are much stronger about recommending
> the use of LilyDev than we were when the CG was orig
Trevor Daniels wrote Monday, May 04, 2015 10:01 PM
> OK, I've created a project on SourceForge and started
> downloading the issues DB from GoogleCode.
[snip]
> You can see the progress here:
> https://sourceforge.net/p/testlilyissues/tickets/
Update: (one ladder, two snakes)
1. I now see that
On 04/05/15 22:39, Wols Lists wrote:
> On 04/05/15 04:02, Carl Sorensen wrote:
>>> 2. Compiling with LilyDev (2.3) and Compiling (4.x)
>> 2.3 is about getting it set up with LilyDev. 4.x is about general work
>> whether with or without LilyDev. We are much stronger about recommending
>> the use o
Wols Lists writes:
> On 04/05/15 04:02, Carl Sorensen wrote:
>>> 2. Compiling with LilyDev (2.3) and Compiling (4.x)
>> 2.3 is about getting it set up with LilyDev. 4.x is about general work
>> whether with or without LilyDev. We are much stronger about recommending
>> the use of LilyDev than w
> But anyways, the main point of this email is to point out that pushing
> debian could cost you developers - I don't know how many people like me
> there are out there, but if I have to use a debian-based system my
> reaction is likely to be "thanks but no thanks". (That said, I think a
The data
On 5/4/15 4:25 PM, "Dan Eble" wrote:
>> But anyways, the main point of this email is to point out that pushing
>> debian could cost you developers - I don't know how many people like me
>> there are out there, but if I have to use a debian-based system my
>> reaction is likely to be "thanks but n
On 5/4/15 3:44 PM, "Trevor Daniels" wrote:
>
>Trevor Daniels wrote Monday, May 04, 2015 10:01 PM
>
>> OK, I've created a project on SourceForge and started
>> downloading the issues DB from GoogleCode.
>[snip]
>> You can see the progress here:
>> https://sourceforge.net/p/testlilyissues/tickets
Reviewers: ,
Message:
I noticed these recently and it seemed appropriate to fix them this way.
Description:
silence C++ warnings
Please review this at https://codereview.appspot.com/231370043/
Affected files (+2, -2 lines):
M lily/beaming-pattern.cc
M lily/page-breaking.cc
Index: lily/be
https://codereview.appspot.com/231370043/diff/1/lily/beaming-pattern.cc
File lily/beaming-pattern.cc (right):
https://codereview.appspot.com/231370043/diff/1/lily/beaming-pattern.cc#newcode170
lily/beaming-pattern.cc:170: int start_dur =
intlog2(static_cast(infos_[i+1].start_moment_.main_part_.d
https://codereview.appspot.com/231370043/diff/1/lily/beaming-pattern.cc
File lily/beaming-pattern.cc (right):
https://codereview.appspot.com/231370043/diff/1/lily/beaming-pattern.cc#newcode170
lily/beaming-pattern.cc:170: int start_dur =
intlog2(static_cast(infos_[i+1].start_moment_.main_part_.d
> On May 3, 2015, at 6:15 PM, David Kastrup wrote:
>
>> CG 3.3.4 Making Patches
>> "git format-patch origin" doesn't work if you type it in literally,
>> but gives "ambiguous argument 'origin' " message.
>
> Shouldn't happen unless you managed to create either a local branch
> named "origin" or
> On May 3, 2015, at 11:02 PM, Carl Sorensen wrote:
>
> I think that it would be great to have you prepare patches for the CG.
> The CG is the least-reviewed manual in our set, so it's probably the
> easiest manual for which to get patches approved.
Will do, once this discussion winds down, and
Hi Federico,
> On May 4, 2015, at 12:32 PM, Federico Bruni wrote:
>
> Hi Paul, thanks for the suggestions.
>
> As Debian Jessie was released few days ago, I was thinking about a new
> LilyDev.
Hey, that’s great timing!
> I think I'll first upgrade to a more recent version of live-build and t
> On May 4, 2015, at 9:10 PM, Paul Morris wrote:
>
> They both have highlighting for c++, .css, and .py files,
> gedit also has it for .scm, .itexi, .itely, and .make files,
> but geany doesn’t have it for these.
> (And neither has it for .ly files.)
This was from the default LilyDev2 with gea
Please review, thanks.
https://codereview.appspot.com/235090043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM.
https://codereview.appspot.com/235090043/diff/1/input/regression/stencil-scale.ly
File input/regression/stencil-scale.ly (right):
https://codereview.appspot.com/235090043/diff/1/input/regression/stencil-scale.ly#newcode8
input/regression/stencil-scale.ly:8: its bounding box.)"
Please use
Looks good! Thanks for posting it. A couple of comments included.
https://codereview.appspot.com/235090043/diff/1/input/regression/stencil-scale.ly
File input/regression/stencil-scale.ly (right):
https://codereview.appspot.com/235090043/diff/1/input/regression/stencil-scale.ly#newcode8
input
On Mon, May 4, 2015 at 4:57 PM, Phil Holmes wrote:
> As promised, a starter list of requirements for the issue handling system,
> to allow us to check potential replacements to Google code.
Hi Phil, thanks for this recap.
This may well be a stupid question, and if so please forgive me, but:
many
On Mon, May 4, 2015 at 12:25 PM, wrote:
> This kind of addition would likely get
> the most useful feedback from people *teaching* LilyPond. We don't have
> a lot of those unless you count "batch teachers", namely documentation
> writers.
Paco would be the obvious person to ask. (Hi Paco!)
Spe
46 matches
Mail list logo
