From: Peter Korsgaard <peter@korsgaard.com>
To: Ricardo Martincoski <ricardo.martincoski@gmail.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH-2021.08.x] package/stress-ng: fix broken URL
Date: Mon, 22 Nov 2021 22:33:04 +0100 [thread overview]
Message-ID: <87lf1fooz3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20211121170534.3807972-1-ricardo.martincoski@gmail.com> (Ricardo Martincoski's message of "Sun, 21 Nov 2021 14:05:34 -0300")
>>>>> "Ricardo" == Ricardo Martincoski <ricardo.martincoski@gmail.com> writes:
> From: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
> Do the same as commit "12c01079bd package/stress-ng: bump to version
> 0.13.05" did for 2022.02 but without the version bump.
> The project URL returns 404 error because:
> Quoting Coling King:
> "Unfortunately when I left Canonical last week they removed my tarballs"
> So use github and update hash.
> Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> [Ricardo: do not bump the version.
> There will be no version clash at sources.buildroot.net since the file
> format changed]
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
> Cc: Romain Naour <romain.naour@gmail.com>
Committed to 2021.02.x and 2021.08.x, thanks.
What about a patch for master?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-22 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 17:05 [Buildroot] [PATCH-2021.08.x] package/stress-ng: fix broken URL Ricardo Martincoski
2021-11-22 21:33 ` Peter Korsgaard [this message]
2021-11-23 10:12 ` Ricardo Martincoski
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=87lf1fooz3.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ricardo.martincoski@datacom.com.br \
--cc=ricardo.martincoski@gmail.com \
--cc=romain.naour@gmail.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