linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Latchesar Ionkov <lucho@ionkov.net>,
	v9fs-developer@lists.sourceforge.net, Sage Weil <sage@redhat.com>,
	Ilya Dryomov <idryomov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH acks] fs/*/Kconfig: drop links to 404-compliant http://acl.bestbits.at
Date: Wed, 20 Dec 2017 07:14:22 -0700	[thread overview]
Message-ID: <20171220071422.5177d2cf@lwn.net> (raw)
In-Reply-To: <20171220135852.7662-1-kilobyte@angband.pl>

On Wed, 20 Dec 2017 14:58:52 +0100
Adam Borowski <kilobyte@angband.pl> wrote:

> This link is replicated in most filesystems' config stanzas.  Referring
> to an archived version of that site is pointless as it mostly deals with
> patches; user documentation is available elsewhere.
> 
> Signed-off-by: Adam Borowski <kilobyte@angband.pl>
> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> Acked-by: Jan Kara <jack@suse.cz>
> Acked-by: Dave Kleikamp <dave.kleikamp@oracle.com>
> Acked-by: David Sterba <dsterba@suse.com>
> Acked-by: "Yan, Zheng" <zyan@redhat.com>
> Acked-by: Chao Yu <yuchao0@huawei.com>
> Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
> Acked-by: Steve French <smfrench@gmail.com>
> ---
> No changes, acks added (Dave Kleikamp's came without CCs).
> 
> Acked: btrfs ceph cifs ext2 f2fs jfs xfs.
> No ack: . 9p ext4 hfsplus jffs2 reiserfs -- but there's no point in caring
> this much for a trivial doc update, molesting the maintainers further is a
> waste of their time.

So how would you like this to go upstream?  I can certainly take it
through docs, but it seems like vfs might be the first choice...?

Thanks,

jon

  reply	other threads:[~2017-12-20 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  5:38 [PATCH] fs/*/Kconfig: drop links to 404-compliant http://acl.bestbits.at Adam Borowski
2017-12-13  6:05 ` Darrick J. Wong
2017-12-13 11:14 ` Jan Kara
2017-12-14  0:44 ` David Sterba
2017-12-14  6:34 ` Yan, Zheng
2017-12-14 10:39 ` Chao Yu
2017-12-14 19:54 ` Jaegeuk Kim
2017-12-15 19:58 ` Steve French
2017-12-20 13:58 ` [PATCH acks] " Adam Borowski
2017-12-20 14:14   ` Jonathan Corbet [this message]
2017-12-20 15:50     ` Adam Borowski
2018-01-01 19:45       ` Jonathan Corbet

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=20171220071422.5177d2cf@lwn.net \
    --to=corbet@lwn.net \
    --cc=adilger.kernel@dilger.ca \
    --cc=dwmw2@infradead.org \
    --cc=ericvh@gmail.com \
    --cc=idryomov@gmail.com \
    --cc=kilobyte@angband.pl \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lucho@ionkov.net \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=rminnich@sandia.gov \
    --cc=sage@redhat.com \
    --cc=tytso@mit.edu \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=viro@zeniv.linux.org.uk \
    /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).