From: Karel Zak <kzak@redhat.com>
To: Daniel Gerber <dg@atufi.org>
Cc: Sean Anderson <seanga2@gmail.com>,
dottedmag@dottedmag.net, id@mbekkema.name, jpeach@apache.org,
util-linux@vger.kernel.org
Subject: Re: [PATCH v2 0/6] unshare: Add support for mapping ranges of user/group IDs
Date: Tue, 18 Jan 2022 12:50:50 +0100 [thread overview]
Message-ID: <20220118115050.jccwbz2hk2323lnl@ws.net.home> (raw)
In-Reply-To: <874k664nlq.fsf@atufi.org>
On Fri, Jan 14, 2022 at 11:29:21AM +0100, Daniel Gerber wrote:
> mem2strcpy(buf, name, sz, sizeof(buf));
> - return strtoul_or_err(name, _("could not parse ID"));
> + return strtoul_or_err(buf, _("could not parse ID"));
Should be fixed in git tree. Thanks for your report!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2022-01-18 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 18:26 [PATCH v2 0/6] unshare: Add support for mapping ranges of user/group IDs Sean Anderson
2021-11-24 18:26 ` [PATCH v2 1/6] include/c: Add abs_diff macro Sean Anderson
2021-11-24 18:26 ` [PATCH v2 2/6] unshare: Add waitchild helper Sean Anderson
2021-11-24 18:26 ` [PATCH v2 3/6] unshare: Add some helpers for forking and synchronizing Sean Anderson
2021-11-24 18:26 ` [PATCH v2 4/6] unshare: Add options to map blocks of user/group IDs Sean Anderson
2021-11-24 18:26 ` [PATCH v2 5/6] unshare: Add option to automatically create user and group maps Sean Anderson
2021-11-24 18:26 ` [PATCH v2 6/6] unshare: Document --map-{groups,users,auto} Sean Anderson
2021-12-01 15:16 ` [PATCH v2 0/6] unshare: Add support for mapping ranges of user/group IDs Karel Zak
2022-01-14 10:29 ` Daniel Gerber
2022-01-14 14:42 ` Sean Anderson
2022-01-14 17:15 ` Daniel Gerber
2022-01-15 0:53 ` Sean Anderson
2022-01-18 11:50 ` Karel Zak [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=20220118115050.jccwbz2hk2323lnl@ws.net.home \
--to=kzak@redhat.com \
--cc=dg@atufi.org \
--cc=dottedmag@dottedmag.net \
--cc=id@mbekkema.name \
--cc=jpeach@apache.org \
--cc=seanga2@gmail.com \
--cc=util-linux@vger.kernel.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 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.