On 5/12/20, 1:33 AM, "lilypond-devel on behalf of Federico Bruni"
wrote:
Thanks to everybody for jumping in so quickly!
-> CS We're now down to 150 issues to be verified. This is great news!
Carl
Am Dienstag, den 12.05.2020, 11:19 + schrieb Trevor:
> Another question:
>
> How do I remove labels no longer relevant (or entered incorrectly!) eg
> Patch:Push for verified issues?
If using the UI, click "Edit" next to the labels, find the one you want
to remove and untick. For the lazy, ty
Another question:
How do I remove labels no longer relevant (or entered incorrectly!) eg
Patch:Push for verified issues?
Trevor
-- Original Message --
From: "Kevin Barry"
To: "Federico Bruni"
Cc: "lilypond-devel"
Sent: 12/05/2020 08:15:02
Subject:
Am Dienstag, den 12.05.2020, 10:03 +0200 schrieb Davide Liessi:
> Dear Federico,
>
> I can contribute too, probably on the same order as Carl:
>
> Il giorno mar 12 mag 2020 alle ore 01:12 Carl Sorensen
> ha scritto:
> > I'll start jumping in, but it will probably be on the order of about 10 per
Dear Federico,
I can contribute too, probably on the same order as Carl:
Il giorno mar 12 mag 2020 alle ore 01:12 Carl Sorensen
ha scritto:
> I'll start jumping in, but it will probably be on the order of about 10 per
> day, give or take.
Can you give me the appropriate permissions?
My GitLab
Il giorno mar 12 mag 2020 alle 08:15, Kevin Barry
ha scritto:
Another handy way to do this is to run git tag --contains
.
(For me this is faster than github.)
Right, I forgot it.
It's faster indeed.
Thanks to everybody for jumping in so quickly!
Hi Federico,
Thank you for the instructions. I will try to help get them done as
well.
On Tue, May 12, 2020 at 12:28:24AM +0200, Federico Bruni wrote:
> In the last comment you should find a commit id (if it's missing you'll have
> to search it).
> The easiest and quickest way to verify that a ce
Hey, we're down to 520!
BTW, instead of scrolling to the bottom of the comments to find the commit id,
it's easier to set the sorting of the comments to "newest first", which puts
the commit ID very near the top.
Maybe I can get us under 500 before I go to bed tonight.
Carl
On 5/11/20, 4:29
Em seg., 11 de mai. de 2020 às 19:29, Federico Bruni
escreveu:
> Start from this list:
>
> https://gitlab.com/lilypond/lilypond/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=Fixed_2_21_0&label_name[]=Status%3A%3AFixed
>
> In the last comment you should find a commit id (if it's miss
Federico,
Thanks for the clear instructions. I'll start jumping in, but it will probably
be on the order of about 10 per day, give or take.
I think we can get this under control eventually
Thanks,
Carl
Federico, you wrote 11/05/2020 23:01:14
I've started verifying issues on Gitlab.
It's quite straightforward, but still boring :-)
I think that most of the times it's "useless", meaning that I can't find any
error.. but sometimes you may find something useful
Il giorno lun 11 mag 2020 alle 17:12, Karlin High
ha scritto:
On 5/11/2020 5:01 PM, Federico Bruni wrote:
If nobody else jumps in, I will probably give up soon.
If someone wants to help, are there step-by-step directions anywhere?
Start from this list:
https://gitlab.com/lilypond/lilyp
On 5/11/2020 5:01 PM, Federico Bruni wrote:
If nobody else jumps in, I will probably give up soon.
If someone wants to help, are there step-by-step directions anywhere?
--
Karlin High
Missouri, USA
Federico Bruni writes:
> Hi all
>
> I've started verifying issues on Gitlab.
> It's quite straightforward, but still boring :-)
> I think that most of the times it's "useless", meaning that I can't
> find any error.. but sometimes you may find s
Hi all
I've started verifying issues on Gitlab.
It's quite straightforward, but still boring :-)
I think that most of the times it's "useless", meaning that I can't
find any error.. but sometimes you may find something useful to report:
a new command to be docu
15 matches
Mail list logo
