All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "François Perrad" <francois.perrad@gadz.org>
Cc: buildroot@busybox.net, Francois Perrad <fperrad@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/libressl: bump to version 3.8.4
Date: Mon, 1 Apr 2024 17:27:07 +0200	[thread overview]
Message-ID: <ZgrSS-71Un9n_B_b@landeda> (raw)
In-Reply-To: <CAAE6iEVy2gvT4wH3Ow3OKzDDpFcR8+CuPtHo-Zz-7S2um_z67A@mail.gmail.com>

François, All,

On 2024-04-01 17:11 +0200, François Perrad spake thusly:
> Le lun. 1 avr. 2024 à 16:17, Yann E. MORIN <[1]yann.morin.1998@free.fr> a
> écrit :
>     Again, yiour From and SoB do not match: [3]fperrad@gmail.com vs.
>     [4]francois.perrad@gadz.org.
> them had never match since I contribute.
> Is it a new rule ?

No it is not a new rule, it just had never been written, checked, nor
enforced.

What would the point of the Sob line if it did not match the author? The
SoB line is there so that the author assesses that they have the right
to contribute their change:

    https://developercertificate.org/

So, if the identity of the author of a change does not match the SoB
line, the SoB line does not mean much...

I just happen to have recently added such a check in my post-applypatch
hook now, so I now notice such discrepancy, and at least Peter is using
it (Romain as well I think):

    https://gitlab.com/buildroot.org/git-hooks/-/commit/c9a8eb6c477dcfe2f2b310b925075c0eb1dcd019

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-04-01 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 17:40 [Buildroot] [PATCH] package/libressl: bump to version 3.8.4 Francois Perrad
2024-04-01 14:17 ` Yann E. MORIN
2024-04-01 15:11   ` François Perrad
2024-04-01 15:27     ` Yann E. MORIN [this message]
2024-04-03  8:42 Francois Perrad
2024-04-03 20:32 ` Yann E. MORIN
2024-05-01 20:17 ` Peter Korsgaard

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=ZgrSS-71Un9n_B_b@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    --cc=fperrad@gmail.com \
    --cc=francois.perrad@gadz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.