Re: [PATCH v2] commit-graph: remove a duplicate assignment

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

 



On 9/27/2019 8:21 AM, Johannes Schindelin wrote:
> Hi,
> 
> 
> On Thu, 26 Sep 2019, Alex Henrie wrote:
> 
>> Signed-off-by: Alex Henrie <alexhenrie24@xxxxxxxxx>
> 
> Hrm, the commit message should reflect Stolee's careful consideration,
> no? An empty commit message won't be helpful e.g. when cherry-picking on
> top of a branch that already has your v1.

I agree that we need more in the commit messages here. It is
helpful to include _why_ you are doing this. Keep in mind
that your cover letter is not recorded with the commit at all.

Further, when updating a patch series, you should re-roll the
entire series as a v2 (preferably as a reply to the original
series). Keep in mind that this patch should NOT be applied
on top of your other series because then 'g' is not assigned
at all. Mechanically, it COULD apply, but it would break
in tests.

Patches 2 and 3 in your series also have feedback that would
be good to apply in your v2.

Thanks,
-Stolee



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux