[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xre
From: |
Stefan Kangas |
Subject: |
Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref" |
Date: |
Mon, 27 Jan 2025 12:36:18 -0600 |
Eli Zaretskii <eliz@gnu.org> writes:
> What I think would be good is to have some kind of data structure
> mapping a source file to the tests which exercise some of the code in
> that source file. The first approximation is to run FOO-tests when
> you modify a file FOO, but some FOO's get used in many places in the
> test suite, so this is not a simple 1:1 relation. Then we could at
> least ask contributors to run the relevant tests as part of the
> submission process.
This sounds like it would be quite useful, indeed.
>> Ideally, we would have something in-band, i.e. an automated email, so
>> that we could avoid this manual work. It would probably be more
>> effective, too. I would be interested to know if there are any
>> pre-existing tools that we could use. It might also be worth
>> considering building a custom one. Maybe we should add looking into
>> something like that to etc/TODO?
>
> It cannot do any harm. But I envision a problem with setting this up
> because the gnu.org infrastructure mighty not be up to the additional
> load. However, we don't need to be afraid of this before someone
> actually works on setting this up.
That's true. I'll see if I can come up with a useful entry.
- Re: Avoid double spaces around abbrevations in Texinfo, (continued)
- Re: Avoid double spaces around abbrevations in Texinfo, Stefan Kangas, 2025/01/24
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Pip Cet, 2025/01/25
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/26
- Running pre-commit tests (was: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref"), Michael Albinus, 2025/01/26
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Stefan Kangas, 2025/01/26
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Stefan Kangas, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Stefan Kangas, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref",
Stefan Kangas <=
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Michael Albinus, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Michael Albinus, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Stefan Kangas, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Michael Albinus, 2025/01/28
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Michael Albinus, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Eli Zaretskii, 2025/01/27
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Michael Albinus, 2025/01/28
- Re: master e54b94c28cd: Use @xref more consistently; "See @ref" -> "@xref", Pip Cet, 2025/01/27