Re: [PATCH v6] suggested changes for reproducibility patchset v6

["Roberto A. Foglietta" <roberto.foglietta@gmail.com>]

On Tue, 17 Jan 2023 at 12:53, Florian Bezdeka
<florian.bezdeka@siemens.com> wrote:
>
> On Sun, 2023-01-15 at 23:46 +0100, Roberto A. Foglietta wrote:
> > On Sun, 15 Jan 2023 at 23:32, Florian Bezdeka
> > <florian.bezdeka@siemens.com> wrote:

> > > > Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> > > > ---
> > >
> > > Comments like changes between versions of your patches should be
> > > mentioned here. Not inside the commit message.
> > >
> >
> > Ok, it seems weird to me but it probably is a standard that automatic
> > software needs. Is that right?
>
> This is how "git am" works. Everything above the "---" line will go
> into the commit message (should be used for story telling), everything
> below that line and in front of the first hunk will be thrown away and
> can be used for further comments/hints for reviewers/maintainers.
>

So, considering that I want to maintain the version revision of the
patch along with the commits, it makes perfect sense that I put them
in the description. After all, the description content is arbitrary to
some degrees. However, I can add the revision log also below the
signature in such a way that some other tools that expect to find,
they will find it. Does this sound good to you?

Best regards, R.