Il giorno sab 30 mag 2015 alle 20:57, David Kastrup ha
scritto:
"Trevor Daniels" writes:
David Kastrup wrote Saturday, May 30, 2015 2:53 PM
At any rate, I can go ask on Savannah if people think that could
be a
viable hosting option.
OK, that seems a sensible next step.
http://lists
Am 31.05.2015 um 07:47 schrieb David Kastrup:
[...]
Well, that was actually more what I considered strange: the lack of
comment on the result/merits rather than on the particular
implementation.
I can just speak for myself, but the actual benefit of this patch was
not obviously clear for me, b
Il giorno sab 30 mag 2015 alle 18:37, Trevor Daniels
ha scritto:
James Lowe wrote Friday, May 29, 2015 8:08 AM
On 28/05/15 18:18, Trevor Daniels wrote:
Given this problem I thought it prudent to see if I could still
import the Issues DB from GoogleCode to Allura in SourceForge. I
starte
Federico Bruni writes:
> Il giorno sab 30 mag 2015 alle 18:37, Trevor Daniels
>
>> Savannah may be prepared to install, maintain and host Allura, or
>> they may be prepared to let us install and maintain it. Don't know
>> who 'us' would be - not me, I have no *nix experience. David says
>> he'l
Federico Bruni wrote Sunday, May 31, 2015 8:14 AM
> Il giorno sab 30 mag 2015 alle 20:57, David Kastrup ha
> scritto:
>> "Trevor Daniels" writes:
>>
>>> David Kastrup wrote Saturday, May 30, 2015 2:53 PM
>>>
At any rate, I can go ask on Savannah if people think that could
be a
I do run Gitlab but can't give any serious feedback. It's like Github, but we
had some limitations with assignment of pull request IIRC.
In all it's maybe not extensive enough for LilyPond, but maybe it can be
integrated with other tools. For example there's gitlab-ci that can be
integrated.
> do we want to take on the commitment to maintain Allura ourselves or
> use the maintained version at SourceForge. Which would we prefer?
Lilypond is a GNU project, thus I strongly favour Savannah as the
primary site for everything.
> (FWIW my preference would be to run Allura at Savannah as o
Werner LEMBERG writes:
>> do we want to take on the commitment to maintain Allura ourselves or
>> use the maintained version at SourceForge. Which would we prefer?
>
> Lilypond is a GNU project, thus I strongly favour Savannah as the
> primary site for everything.
>
>> (FWIW my preference would
Il giorno dom 31 mag 2015 alle 10:23, David Kastrup ha
scritto:
Personally, I'd consider it better to work with a combined site in
this
respect since it would mean that any tools we develop for our
workflows
(like our own personal git-cl fork) are not LilyPond-only.
IIUC, there's already thi
>>> (FWIW my preference would be to run Allura at Savannah as our
>>> primary DB, with a backup being maintained at SF, which I would be
>>> happy to do on a monthly basis.)
>>
>> This sounds like a sensible approach.
>
> Given the reports that SourceForge distributes Adware (and there
> even have
Patch counted down - please push
https://codereview.appspot.com/240950043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch counted down - please push
https://codereview.appspot.com/241760043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
Here is the current patch countdown list. The next countdown will
(hopefully) be on June 3rd.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sor
David Kastrup wrote Sunday, May 31, 2015 11:02 AM
> Given the reports that SourceForge distributes Adware (and there even
> have been virus-ridden versions of it) on its Windows installers, I'm
> somewhat wary here. It would be sort of strange to use project
> facilities there without offering d
Hello,
Am 31.05.2015 um 03:07 schrieb k-ohara5...@oco.net:
I realize I am changing my opinion here on a few points:
[…]
(A convert-ly rule may be needed… maybe in any case to
change whiteout to whiteout-box? ...or maybe not?)
Looking at the existing uses of \whiteout Xxx.whiteout, it does
Federico Bruni wrote Sunday, May 31, 2015 11:09 AM
> Actually, Google Code exports to Github. I tried, just to see what
> happens and it turned out that the standard export works only for
> issues <1000. Here's the FAQ:
> https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ#Error_%22P
Werner LEMBERG wrote Sunday, May 31, 2015 11:41 AM
(FWIW my preference would be to run Allura at Savannah as our
primary DB, with a backup being maintained at SF, which I would be
happy to do on a monthly basis.)
>>>
>>> This sounds like a sensible approach.
>>
>> Given the repor
I've pushed
Issue 4417 / 3: Fix png filename handling
authorMasamichi Hosoda
Sun, 24 May 2015 14:20:30 + (23:20 +0900)
committer Masamichi Hosoda
Sun, 31 May 2015 13:27:28 + (22:27 +0900)
commit6a59207988b737482012aee97c6d3d5c1458a750
Issue 4417 / 2: Use ly
Reviewers: J_lowe,
Message:
I've pushed.
Issue 4420: Add Netpbm messages to verbose output
authorMasamichi Hosoda
Mon, 25 May 2015 14:41:16 + (23:41 +0900)
committer Masamichi Hosoda
Sun, 31 May 2015 13:39:19 + (22:39 +0900)
commitb666e5959e3eb170e57bb1937f
On Sun, 31 May 2015 05:03:05 -0700, Simon Albrecht
wrote:
(A convert-ly rule may be needed… maybe in any case to
change whiteout to whiteout-box? ...or maybe not?)
Looking at the existing uses of \whiteout Xxx.whiteout, it does seem
best to leave the plain box whiteout in existing scores. Co
I have some questions about this.
> void
> Auto_change_iterator::process (Moment m)
> {
> Music_wrapper_iterator::process (m);
>
> Moment now = get_outlet ()->now_mom ();
> Moment *splitm = 0;
> if (start_moment_.main_part_.is_infinity () && start_moment_ < 0)
> start_moment_ = now;
Reviewers: ,
Description:
clean up finding & changing of contexts in C++
Combine the key feature of Change_iterator and Auto_change_iterator
into a common function (favoring the logic of Change_iterator).
Define functions for various context-search loops.
Please review this at https://coderevi
2015-05-28 10:41 GMT+02:00 David Kastrup :
> James Lowe writes:
>
>> On 28/05/15 07:20, David Kastrup wrote:
>>> And no idea what this means for Patchy.
>>
>> Well you cannot run any of the test/accept/reject scripts.
>>
>> The last two are not a huge deal but test-patchy means I probably won't
>>
Dan Eble writes:
> I have some questions about this.
>
>> void
>> Auto_change_iterator::process (Moment m)
>> {
>> Music_wrapper_iterator::process (m);
>>
>> Moment now = get_outlet ()->now_mom ();
>> Moment *splitm = 0;
>> if (start_moment_.main_part_.is_infinity () && start_moment_ < 0
Trevor Daniels treda.co.uk> writes:
> The next step is to decide our preference: do we want to take on the
> commitment to maintain Allura ourselves or use the maintained version at
> SourceForge. Which would we prefer? (FWIW my preference would be
> to run Allura at Savannah as our primary DB,
25 matches
Mail list logo
