public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux F2FS Dev Mailing List 
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [GIT PULL] f2fs update for 4.10
Date: Wed, 14 Dec 2016 17:18:57 -0800	[thread overview]
Message-ID: <20161215011857.GA3540@kroah.com> (raw)
In-Reply-To: <CA+55aFyvoaBXmyO56_uwMEtovMD7dW8YFMM9ZaahcBLVoE=CSg@mail.gmail.com>

On Wed, Dec 14, 2016 at 04:38:32PM -0800, Linus Torvalds wrote:
> On Wed, Dec 14, 2016 at 11:18 AM, Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > BTW, I just downloaded mainline, and tried to build a debian package but
> > failed due to missing Documentation/Changes.
> >
> > I've found out that it was renamed by commit 186128f753
> >  ("docs-rst: add documents to development-process")
> >
> > And when taking a look at its description, it was supposed to do symlink for
> > document files, but did rename all of them.
> 
> Indeed.
> 
> Tssk. I've added the one symlink. Maybe we should add the others too,
> but for now let's keep it minimal.

Crap, I missed that in the patch I acked, I should have noticed that.

Thanks for the symlink, Mauro, want to make the rest of the files actual
symlinks as well, instead of just the rename?

thanks,

greg k-h

  reply	other threads:[~2016-12-15  1:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 22:15 [GIT PULL] f2fs update for 4.10 Jaegeuk Kim
2016-12-14 17:12 ` Linus Torvalds
2016-12-14 18:40   ` Jaegeuk Kim
2016-12-14 19:18     ` [f2fs-dev] " Jaegeuk Kim
2016-12-15  0:38       ` Linus Torvalds
2016-12-15  1:18         ` Greg Kroah-Hartman [this message]
2016-12-15  9:33           ` Mauro Carvalho Chehab

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=20161215011857.GA3540@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=torvalds@linux-foundation.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