From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] valgrind: bump version to 3.13.0
Date: Mon, 16 Apr 2018 18:08:54 +0200 [thread overview]
Message-ID: <20180416180854.5c729f1f@gmx.net> (raw)
In-Reply-To: <20180416145613.5d8d7fb9@windsurf.numericable.fr>
Hello Thomas,
On Mon, 16 Apr 2018 14:56:13 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Sun, 15 Apr 2018 22:22:41 +0200, Peter Seiderer wrote:
> > - update site
> > - remove 0004-Fixes-for-musl-libc.patch (applied upstream, see [1])
> >
> > [1] https://sourceware.org/git/?p=valgrind.git;a=commit;h=f8f1e9cb434cc97ce16586437407a6ac7e6a74a7
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> You're removing the only patch that was touching configure.ac, so I
> believe AUTORECONF = YES is no longer necessary in valgrind.mk. Do you
> confirm ?
Ups, yes, you are right....will send a v2 fixing it (and adding license file hashes)....
Regards,
Peter
>
> Best regards,
>
> Thomas
prev parent reply other threads:[~2018-04-16 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 20:22 [Buildroot] [PATCH v1] valgrind: bump version to 3.13.0 Peter Seiderer
2018-04-16 12:56 ` Thomas Petazzoni
2018-04-16 16:08 ` Peter Seiderer [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=20180416180854.5c729f1f@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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