From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 1/2] linux-custom: Install config and map file to /boot
Date: Mon, 20 Apr 2020 21:46:52 +0200 [thread overview]
Message-ID: <20200420214652.1a14ef0a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200420160316.lwhwzmfvvkv2j5wf@yssyq.m.ilbers.de>
Am Mon, 20 Apr 2020 18:03:16 +0200
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> On Mon, Apr 20, 2020 at 03:07:29AM -0700, vijai kumar wrote:
> > > Yes, e.g.
> > > https://groups.google.com/d/msg/isar-users/knMKY-9b5Nw/aDIpgN1MCQAJ
> > > has From: Vijai Kumar K <Vijaikumar_...@mentor.com <javascript:>>
> > > as the first line,
> > > and the latter patches don't.
> >
> > Yes. Sorry about that. I have fixed my configuration. Here after it
> > should come with a proper from.
>
> No problem! Just an explanation how one could verify that by looking
> at the patch on the list.
That is not the duty of the maintainer. If contributors get their email
wrong its their problem. If weird IT of contributors prevents them from
sending raw emails, that is a problem of those companies. Because their
contributions will not show up in i.e. "git shortlog -sne | grep
company" ... so they might not get the "credits" ... whatever that
means to those companies should not be the maintainers business.
It might be a nice finding and the maintainer could comment on it, but
you should not waste your time.
On the list you will see the "From" header of the mail, an override
would be an addition "From" in the body. If the "From" in the mail is
not the "Signed-off" that would be an indication. Once you "git am" you
can see the same "problem" in your git.
Henning
> With kind regards,
> Baurzhan.
>
next prev parent reply other threads:[~2020-04-20 19:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 17:14 [PATCH] " Vijai Kumar K
2020-03-17 17:19 ` vijai kumar
2020-03-17 17:39 ` Jan Kiszka
2020-03-25 7:07 ` cedric_hombourger
2020-04-03 7:28 ` vijai kumar
2020-04-03 7:29 ` vijai kumar
2020-03-17 17:32 ` Jan Kiszka
2020-03-18 5:53 ` vijai kumar
2020-03-18 7:34 ` Henning Schild
2020-03-18 13:03 ` vijai kumar
2020-03-18 13:21 ` [PATCH v2] " Vijai Kumar K
2020-03-23 6:12 ` Jan Kiszka
2020-03-23 6:53 ` Henning Schild
2020-03-23 6:55 ` Jan Kiszka
2020-03-23 7:49 ` vijai kumar
2020-03-23 9:13 ` Henning Schild
2020-03-23 9:24 ` vijai kumar
2020-03-23 10:40 ` Henning Schild
2020-03-23 13:40 ` [PATCH v3 1/2] " Vijai Kumar K
2020-03-23 13:40 ` [PATCH v3 2/2] meta/recipes-kernel: Replace cp with install Vijai Kumar K
2020-04-17 15:05 ` [PATCH v3 1/2] linux-custom: Install config and map file to /boot Baurzhan Ismagulov
2020-04-17 18:44 ` vijai kumar
2020-04-17 18:59 ` vijai kumar
2020-04-20 9:28 ` Baurzhan Ismagulov
2020-04-20 10:07 ` vijai kumar
2020-04-20 16:03 ` Baurzhan Ismagulov
2020-04-20 19:46 ` Henning Schild [this message]
2020-04-20 19:51 ` Henning Schild
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=20200420214652.1a14ef0a@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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