devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Denis Ciocca <denis.ciocca@st.com>,
	devicetree@vger.kernel.org,
	Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH] dt-bindings: iio: st-sensors: Fix repeated text
Date: Wed, 29 Mar 2023 10:39:08 +0200	[thread overview]
Message-ID: <CACRpkdbM_Dron8irHbP77MW2=Yq6o2MAUdYSTE1jcfSHsXZfQg@mail.gmail.com> (raw)
In-Reply-To: <23b2de4b-1198-bfcc-fd74-285da9af4fb3@linaro.org>

On Wed, Mar 29, 2023 at 10:25 AM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:

> Please drop the autogenerated scripts/get_maintainer.pl CC-entries from
> commit msg (Jonathan's, Lars', Rob's, mine, DT list). There is no single
> need to store automated output of get_maintainers.pl in the git log. It
> can be easily re-created at any given time, thus its presence in the git
> history is redundant and obfuscates the log.
>
> If you need it for your own patch management purposes, keep it under the
> --- separator.

Oh yeah I've seen that people do this these days, just (old) bad habits.

I am trying to use b4 for this going forward, it always does the right thing.

Thanks!
Linus Walleij

  reply	other threads:[~2023-03-29  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  7:46 [PATCH] dt-bindings: iio: st-sensors: Fix repeated text Linus Walleij
2023-03-29  8:25 ` Krzysztof Kozlowski
2023-03-29  8:39   ` Linus Walleij [this message]
2023-04-01 15:15     ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACRpkdbM_Dron8irHbP77MW2=Yq6o2MAUdYSTE1jcfSHsXZfQg@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=denis.ciocca@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).