From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] util-linux: bump to version 2.33
Date: Wed, 7 Nov 2018 22:18:48 -0200 (BRST) [thread overview]
Message-ID: <1716564137.733509.1541636328074.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20181107023217.3564-1-casantos@datacom.com.br>
Superseded-by: https://patchwork.ozlabs.org/patch/994565/
next prev parent reply other threads:[~2018-11-08 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 2:32 [Buildroot] [PATCH] util-linux: bump to version 2.33 Carlos Santos
2018-11-08 0:18 ` Carlos Santos [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-08 0:16 Carlos Santos
2018-11-10 8:40 ` Peter Korsgaard
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=1716564137.733509.1541636328074.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--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