Hi Shou-Chi,

Shou-Chi Chen <tuxs...@gmail.com> writes:

> I've subscribed to the coreutils mailing lists and am still observing how 
> things work.
> I'm curious about where to send patches. I read the guide in `README-hacking` 
> at the
> project root, which states that patches for fixes or new features should be 
> sent to
> the bug mailing list (bug-coreut...@gnu.org). However, I also noticed that 
> some people
> send their patches as attachments to the discussion mailing list 
> (coreutils@gnu.org)
> as well. Are both of these acceptable?

I had a similar question when I started contributing. I will copy
Pádraig's response here [1]:

>> Also, I didn't see there was a bug-coreutils mailing list. Would that
>> be a better place to send patches in the future? Thanks.
>
> bug-coreutils is where you want to create a _user_ trackable / findable
> report under https://bugs.gnu.org/
> The main coreutils is best for design discussions,
> and non user facing stuff in general.

So if you are reporting and/or fixing a real bug, the best place is
probably bug-coreut...@gnu.org so it can be tracked.

If you are, for example, fixing a test case that fails on some platform
for reasons unrelated to coreutils or fixing warnings for new compiler
versions, then coreutils@gnu.org will work fine.

Since we both had similar questions, I'll look later to see if it can be
documented more clearly.

Collin

[1] https://lists.gnu.org/archive/html/coreutils/2024-02/msg00004.html

Reply via email to