From: Robbie Harwood <rharwood@redhat.com>
To: development@efficientek.com
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
dkiper@net-space.pl, darren.kenny@oracle.com, ps@pks.im,
dja@axtens.net
Subject: Re: [PATCH v2 4/4] Update gnulib version and drop all gnulib patches
Date: Thu, 27 Jan 2022 10:08:53 -0500 [thread overview]
Message-ID: <jlgr18tusfu.fsf@redhat.com> (raw)
In-Reply-To: <20220126210622.5a0edaf6@crass-HP-ZBook-15-G2>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
Glenn Washburn <development@efficientek.com> writes:
> Robbie Harwood <rharwood@redhat.com> wrote:
>
>
>> -scriptversion=2019-01-04.17; # UTC
>> +scriptversion=2021-04-11.09; # UTC
>
> This version doesn't match and is older than the version in the
> $GNULIB_REVISION below. Was there a reason why you didn't want to
> update the bootstrap script to that revision level?
No, I just had a local checkout with a slightly older version and forgot
to commit it for update :) Will fix.
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-01-27 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:09 [PATCH v2 0/4] Update gnulib and drop patches Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 1/4] Use visual indentation in config.h.in Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 2/4] Drop gnulib fix-base64.patch Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 3/4] Drop gnulib no-abort.patch Robbie Harwood
2022-01-26 22:09 ` [PATCH v2 4/4] Update gnulib version and drop all gnulib patches Robbie Harwood
2022-01-27 3:06 ` Glenn Washburn
2022-01-27 15:08 ` Robbie Harwood [this message]
2022-01-27 2:55 ` [PATCH v2 0/4] Update gnulib and drop patches Glenn Washburn
2022-01-27 16:46 ` Robbie Harwood
2022-01-27 17:28 ` Robbie Harwood
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=jlgr18tusfu.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=development@efficientek.com \
--cc=dja@axtens.net \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=ps@pks.im \
/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.