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
Subject: Re: [PATCH acks] fs/*/Kconfig: drop links to 404-compliant http://acl.bestbits.at
Date: Mon, 1 Jan 2018 12:45:22 -0700	[thread overview]
Message-ID: <20180101124522.150149ba@lwn.net> (raw)
In-Reply-To: <20171220155024.ayldflt2pgdd4pf2@angband.pl>

On Wed, 20 Dec 2017 16:50:24 +0100
Adam Borowski <kilobyte@angband.pl> wrote:

> > 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...?  
> 
> Good question.  I submitted it in one piece, to reduce spam (plenty of
> mostly two-line changes to elebenty filesystems' prose), and no one pays me
> per-commit, but splitting Documentation/ from fs/*/Kbuild might be
> reasonable.
> 
> Al: would you prefer to take it as a single commit, as Doc + fs, or chopped
> into tiny bits?

I've gone ahead and applied this.

jon

      reply	other threads:[~2018-01-01 19:45 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
2017-12-20 15:50     ` Adam Borowski
2018-01-01 19:45       ` Jonathan Corbet [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=20180101124522.150149ba@lwn.net \
    --to=corbet@lwn.net \
    --cc=kilobyte@angband.pl \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).