[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: contributing to Emacs

From: Po Lu
Subject: Re: contributing to Emacs
Date: Sun, 18 Jun 2023 21:29:09 +0800
User-agent: Gnus/5.13 (Gnus v5.13)

Konstantin Kharlamov <hi-angel@yandex.ru> writes:

> On Sun, 2023-06-18 at 20:09 +0800, Po Lu wrote:
>> Konstantin Kharlamov <hi-angel@yandex.ru> writes:
>> > Ideally, each commit in the repository should contain minimal functional
>> > changes. It allows for easier code review at the moment and for better
>> > figuring
>> > out why some change was done later in the life of the project. Usually at
>> > this
>> > point I refer people to this old article from kernel HID subsystem
>> > maintainer
>> > and libinput creator
>> > http://who-t.blogspot.com/2009/12/on-commit-messages.html
>> > Old — but gold! 😄
>> That's the purpose of ChangeLog, not the VCS.
>> > When project contributions are done via mailing list (such as kernel, gdb,
>> > gcc,
>> > and in the past were also Xorg and Mesa), you usually turn a number of
>> > commits
>> > to separate patches and send them. E.g. here's one example:
>> > https://lore.kernel.org/dri-devel/20230612104658.1386996-1-tvrtko.ursulin@linux.intel.com/
>> > it starts with a "zero patch" that is the title of the series, and then
>> > individual patches follow.
>> Mesa and Linux are hardly all the world, and that wasn't my experience
>> with GDB or GCC development.
> I am not sure what you mean. Here's GCC ML with patches for the last month
> https://gcc.gnu.org/pipermail/gcc-patches/2023-May/thread.html You can see 
> they
> send series as well. Here's an arbitrary cover letter "zero patch" for a 
> series
> https://gcc.gnu.org/pipermail/gcc-patches/2023-May/618426.html

Where is it said that GCC development prefers changes to be submitted in
this format?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]