util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: RFC [patch] adding docstrings
Date: Mon, 22 Dec 2014 11:11:06 +0100	[thread overview]
Message-ID: <20141222101106.GA7668@x2.net.home> (raw)
In-Reply-To: <1419086574.2592978.205177769.60905F6A@webmail.messagingengine.com>

On Sat, Dec 20, 2014 at 03:42:54PM +0100, Benno Schulenberg wrote:
> By the way, there was some talk of obsoleting / scrapping / deleting
> some of the utils.  Are there still such plans?  If so, it is maybe

 Documentation/deprecated.txt

 but I don't think anything is planned for the next release(s), so it's
 probably fine to add docscript everywhere.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2014-12-22 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 20:20 RFC [patch] adding docstrings Benno Schulenberg
2014-12-18  9:20 ` Adam Sampson
2014-12-18 20:29   ` Benno Schulenberg
2014-12-19  9:09 ` Karel Zak
2014-12-20 14:42   ` Benno Schulenberg
2014-12-22 10:11     ` 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=20141222101106.GA7668@x2.net.home \
    --to=kzak@redhat.com \
    --cc=bensberg@justemail.net \
    --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;
as well as URLs for NNTP newsgroup(s).