From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 0/7] pull: various small changes
Date: Mon, 29 Jun 2015 11:49:13 +0200 [thread overview]
Message-ID: <20150629094913.GV1992@ws.net.home> (raw)
In-Reply-To: <1435520605-4296-1-git-send-email-kerolasa@iki.fi>
On Sun, Jun 28, 2015 at 08:43:18PM +0100, Sami Kerola wrote:
> But deprecations can be tricky, so it would be great to hear if I
> assumptions about reset(1) and the last-deprecated are right or wrong.
The old last(1) implementation deprecation is expected and planned,
so it's fine and I think it's also fine to add the reset script
between deprecated stuff.
Applied, thanks.
> build-sys: add minimal whitespace build directory support
I don't like this patch. I don't think it's good idea to add warning
about libtools limitations to the all build systems. If we really need
such warning than it has to be in the LT_INIT.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-06-29 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 19:43 [PATCH 0/7] pull: various small changes Sami Kerola
2015-06-28 19:43 ` [PATCH 1/7] last-deprecated: remove from source tree Sami Kerola
2015-06-28 19:43 ` [PATCH 2/7] zramctl: add link to kernel documentation Sami Kerola
2015-06-28 19:43 ` [PATCH 3/7] cal: fix memory leaks [valgrind] Sami Kerola
2015-06-28 19:43 ` [PATCH 4/7] docs: unify mkswap(8) with swapon(8) about holes warning Sami Kerola
[not found] ` <CADNa6_39RU7RQRpd0oG1KAVT2Yo0Z1fi6roy6cQXCeNkeFQG5A@mail.gmail.com>
2015-06-29 8:09 ` Sami Kerola
2015-06-28 19:43 ` [PATCH 5/7] build-sys: add minimal whitespace build directory support Sami Kerola
2015-06-28 19:43 ` [PATCH 6/7] getopt: use $(...) command substitution in example script [shellcheck] Sami Kerola
2015-06-28 19:43 ` [PATCH 7/7] reset: deprecate the script, and remove reset.033c Sami Kerola
2015-06-29 9:49 ` Karel Zak [this message]
2015-06-29 10:14 ` [PATCH 0/7] pull: various small changes Ruediger Meier
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=20150629094913.GV1992@ws.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox