Re: [PATCH v2 2/3] CodingGuidelines: hint why we value clearly written log messages

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

Subject: Re: [PATCH v2 2/3] CodingGuidelines: hint why we value clearly written log messages
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Thu, 27 Jan 2022 10:35:47 -0800
Cc: Git List <git@xxxxxxxxxxxxxxx>
In-reply-to: <CAPig+cRNwjaRtqLcGrz-oE+C+atAHiRgXTDTUTisgDabkOvcMw@mail.gmail.com> (Eric Sunshine's message of "Thu, 27 Jan 2022 02:31:34 -0500")
References: <xmqqilua89z5.fsf@gitster.g> <20220126234205.2923388-1-gitster@pobox.com> <20220126234205.2923388-3-gitster@pobox.com> <CAPig+cRNwjaRtqLcGrz-oE+C+atAHiRgXTDTUTisgDabkOvcMw@mail.gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes:

> Nit: Dropping "much" makes this sound a bit better grammatically:

Thanks.

References:
- [RFC] Contributor doc: more on the proposed log message
  - From: Junio C Hamano
- [PATCH v2 0/3] contributor doc update around log messages
  - From: Junio C Hamano
- [PATCH v2 2/3] CodingGuidelines: hint why we value clearly written log messages
  - From: Junio C Hamano
- Re: [PATCH v2 2/3] CodingGuidelines: hint why we value clearly written log messages
  - From: Eric Sunshine

Prev by Date: Re: [PATCH v2] test-lib: unset trace2 parent envvars
Next by Date: Re: WARNING: terminal is not fully functional
Previous by thread: Re: [PATCH v2 2/3] CodingGuidelines: hint why we value clearly written log messages
Next by thread: [PATCH v3 0/3] contributor doc update around log messages
Index(es):
- Date
- Thread

[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