From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stefan Agner <stefan@agner.ch>
Cc: yann.morin.1998@free.fr, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] [master] boot/grub2: fix build race condition
Date: Thu, 4 Aug 2022 16:05:18 +0200 [thread overview]
Message-ID: <20220804160518.75e7a753@windsurf> (raw)
In-Reply-To: <26aed3ae6ff8f346b8269669817df0ef@agner.ch>
On Thu, 04 Aug 2022 15:38:28 +0200
Stefan Agner <stefan@agner.ch> wrote:
> > We require all patches to have a proper commit log, with commit title +
> > description, and a Signed-off-by line. Also, we need to have the
> > upstream status of the patch, i.e where it has been submitted (or taken
> > from).
>
> The problem is, this patch is not generated from a source repository but
> simply using patch from the release tarball. The source repository does
> not contain Makefile.in, which needs to be patched...
>
> So a "proper commit log" as such is not possible. I can of course fake
> it and make it look like the patch got generated from a commit, but not
> sure if that is sensible?
Regardless of how the patch is generated, we want it to have a commit
log + description as well as an upstream status.
A basic way:
tar xf grub-2.06.tar.xz
cd grub-2.06
git init
git add .
git commit -s -m "Initial import"
and now do your changes
Of course, it's not going to be a patch that we can apply to the
upstream Git repository, but at least you will have the proper tooling to
create a patch that a commit title, description, SoB and contains an
indicate of its upstream status.
Alternatively, I see you're avoiding autoreconf. Any reason to do so?
Autoreconf doesn't work? (I know with some older grub versions,
autoreconf was problematic, so perhaps it is still the case).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-04 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 11:45 [Buildroot] [PATCH] [master] boot/grub2: fix build race condition Stefan Agner
2022-08-04 13:12 ` Thomas Petazzoni via buildroot
2022-08-04 13:38 ` Stefan Agner
2022-08-04 14:05 ` Thomas Petazzoni via buildroot [this message]
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=20220804160518.75e7a753@windsurf \
--to=buildroot@buildroot.org \
--cc=stefan@agner.ch \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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