Both for their respective Savannah instances:
- https://savannah.gnu.org/
- https://savannah.nongnu.org/
Signed-off-by: Sam James
---
metadata.dtd | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/metadata.dtd b/metadata.dtd
index 5f65033..4ee2741 100644
--- a/metadata.dtd
+++
> On Mon, 29 Aug 2022, Sam James wrote:
> Both for their respective Savannah instances:
> - https://savannah.gnu.org/
> - https://savannah.nongnu.org/
I think they should be called savannah and savannah-nongnu because gnu
isn't savannah. There are many GNU packages that are hosted elsewhere,
> On 29 Aug 2022, at 22:42, Ulrich Mueller wrote:
>
>> On Mon, 29 Aug 2022, Sam James wrote:
>
>> Both for their respective Savannah instances:
>> - https://savannah.gnu.org/
>> - https://savannah.nongnu.org/
>
> I think they should be called savannah and savannah-nongnu because gnu
> isn
> On Mon, 29 Aug 2022, Sam James wrote:
>> I think they should be called savannah and savannah-nongnu because gnu
>> isn't savannah. There are many GNU packages that are hosted elsewhere,
>> e.g. gcc, gdb, glibc, or binutils.
> It's a fair point and it's one I raised in #gentoo-qa, although t
On Sun, Aug 28, 2022 at 07:34:57AM -0500, Gordon Pettey wrote:
> IMHO... much preferable to align these with names, i.e. vega10, vega20,
> rather than some ID number. USE should be self-explanatory wherever
> possible.
>
> On Sun, Aug 28, 2022 at 6:01 AM Yiyang Wu
> wrote:
>
Thanks for the sugg