public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] newer kernels (e.g. v5.19) do not include objtool anymore in linux-header fixed
Date: Thu, 3 Nov 2022 13:07:40 +0100	[thread overview]
Message-ID: <CAJGKYO79K5z3xEYxRCG3uPsjv4xPUtVV1jS-cs=wuo+Lvz_pQA@mail.gmail.com> (raw)
In-Reply-To: <6813218.9J7NaK4W3v@home>

Il giorno gio 3 nov 2022 alle ore 07:47 Uladzimir Bely
<ubely@ilbers.de> ha scritto:

> The patch is mailformed here. Looks like it was sent not via "git send-email",
> but just copy-pasted to the mail body.
>
> Could you please send v2?
>
> > -    if [ -n "${CONFIG_STACK_VALIDATION}" ]; then
> > +    if [ -n "${CONFIG_STACK_VALIDATION}" -o -n "${CONFIG_HAVE_OBJTOOL}" ];
> > then (cd ${O}; find tools/objtool -type f -executable) >>${obj_hdr_files}
> > fi
> >      if [ -n "${CONFIG_GCC_PLUGINS}" ]; then
>
>
> --
Hi Uladzimir,

I have configured git send-email but I still have problems with SMTP
authentication due to two multiple factor authentication settings on
my gmail account. However, I found this which is interesting and also
fits with my perception. I think that the attached patches should be
accepted as well as inline. IMHO, obviously.

https://stackoverflow.com/questions/68238912/how-to-configure-and-use-git-send-email-to-work-with-gmail-to-email-patches-to

Note to developers and maintainers of glibc, Buildroot, and other
projects which require the use of git send-email to send patches: if I
wasn't a professional developer, there's not a chance in heck I could
submit a patch, even if I knew how to expertly code and had important
changes to make. The barrier of entry into git, rebasing, formatting
patches, configuring git send-email, etc., is just too high. Consider
lowering the barrier to entry by using modern tools such as GitHub,
GitLab, or BitBucket to manage your projects and accept patches, in
lieu of emailed patches, email mailing lists, and git send-email. One
huge success case of making this transition recently is KiCad. In 2020
they were still using emailed git patches. Now, they have migrated
fully to GitLab: https://gitlab.com/kicad. Their issue reporting and
management, for instance, is sooooo much easier now!:
https://gitlab.com/kicad/code/kicad/-/issues. Even regular users who
are non-programmers are easily able to report issues now, whereas
before, KiCad was using https://launchpad.net/kicad, which was more
tedious and difficult.

At a minimum, do people a favor and please direct people to this
answer to help them set up git send-email, and help keep this answer
up-to-date.

Best regards, -R

  parent reply	other threads:[~2022-11-03 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 19:09 Roberto A. Foglietta
2022-11-03  6:47 ` Uladzimir Bely
2022-11-03  8:08   ` Bezdeka, Florian
2022-11-03 12:07   ` Roberto A. Foglietta [this message]
2022-11-03 12:19     ` Roberto A. Foglietta

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='CAJGKYO79K5z3xEYxRCG3uPsjv4xPUtVV1jS-cs=wuo+Lvz_pQA@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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