Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: rc1 planning
Date: Wed, 24 Feb 2016 15:50:21 +0100	[thread overview]
Message-ID: <201602241550.21863.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20160224125641.kw2t37ofjhmealej@ws.net.home>

On Wednesday 24 February 2016, Karel Zak wrote:
>  Hi,
>
>  I'd like to release v2.28-rc1 ASAP, but the rest of this week and
> all next week I have vacation (and all next week I'm going to be
> off-line somewhere in Atlantic). So, my plan is 7th or 8th March.
>
>  remaining issues:
>
>   * btrfs loop devs in libmount
>
>   * libblkid vs. CDROMs (check if last two 2K sectors are readable,
> if not reduce probing area)    [me]
>
>   * add time formatting functions for ISO and ctime [not urgent]
>
>   * cleanup openat() related function [not urgent, Rudi?]

I've changed my mind a bit about lib/at.c removal because it's used by 
sysfs.c and we would lose libblkid and fdisk on non-linux systems. I 
will review first whether we could build libblkid without sysfs for 
non-Linux.

Regarding my stupid commit ...
  8b9cf26a "lib: fix unused parameters and variables"
... next time I would try to add our new "NO_UNUSED_WARN_CFLAGS" just 
for single source files. Not using __unused macros would keep our 
heavily ifdef'ed sources more readable.

>   * add --zeroout to blkdiscard [me]
>
>   * fix look(1) [https://github.com/karelzak/util-linux/issues/284]
>
>   * cleanup docs, gtk-doc warnings, etc.

My favorite warning one could fix is this one:

Making all in libblkid/docs
make[2]: Entering directory `/home/rudi/devel/util-linux/libblkid/docs'
make[2]: Circular libblkid-sections.txt <- scan-build.stamp dependency 
dropped.

>   * ???
>
>
>     Karel

  reply	other threads:[~2016-02-24 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 12:56 rc1 planning Karel Zak
2016-02-24 14:50 ` Ruediger Meier [this message]
2016-02-24 17:47   ` Karel Zak
2016-03-04 21:22 ` [PATCH] setarch: fix personality syscall return code check Dmitry V. Levin
2016-03-07 13:54   ` Karel Zak

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=201602241550.21863.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox