From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches being worked on
Date: Sun, 28 Mar 2021 15:52:00 +0200 [thread overview]
Message-ID: <cb3c25ab-df9d-196b-d60b-0e3503b158f4@ipfire.org> (raw)
In-Reply-To: <a7b57926-e717-566c-9dd9-dbc26462c9ae@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Hi All,
I have dropped bash from my updates.
I was able to confirm, by review of the patches and tarball files that
bash-4.0-paths-1.patch
bash-4.0-profile-1.patch
bash-3.2-ssh_source_bash.patch
are all still needed.
However the bash-5.0 set of 18 patches I could not find all of the patch
parts in the tarball files. Doing the build caused several hunks to fail
because a match could not be found. Some matched because the changes
were now incorporated.
Reviewing the first patch there were several of the lines from the
previous version that are no longer in the newer tarball files.
However I am unable to tell if this is because the changes are now
incorporated in the tarball files but in a different way to the patch or
if they are missing and a new set of patches is required to implement
the same changes.
This update needs someone else to work on it with better skills than mine.
Regards,
Adolf.
On 28/03/2021 10:33, Adolf Belka wrote:
> Hi All,
>
>
> For info I am working on the following update patches:-
>
> bash
> binutils
> bison
> bzip2
> diffutils
> ed
> gawk
> lm_sensors
> perl
>
> Regards,
>
> Adolf
>
--
Sent from my laptop
next prev parent reply other threads:[~2021-03-28 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 8:33 Adolf Belka
2021-03-28 13:52 ` Adolf Belka [this message]
2021-03-29 20:14 ` Michael Tremer
2021-03-29 20:11 ` Michael Tremer
2021-03-29 20:46 ` Adolf Belka
2021-03-29 21:22 ` Michael Tremer
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=cb3c25ab-df9d-196b-d60b-0e3503b158f4@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox