From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f195.google.com ([209.85.223.195]:35946 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752520AbeGAUZc (ORCPT ); Sun, 1 Jul 2018 16:25:32 -0400 Received: by mail-io0-f195.google.com with SMTP id k3-v6so12975138iog.3 for ; Sun, 01 Jul 2018 13:25:32 -0700 (PDT) MIME-Version: 1.0 References: <20180701123129.GS30522@ZenIV.linux.org.uk> <20180701200539.GU30522@ZenIV.linux.org.uk> In-Reply-To: <20180701200539.GU30522@ZenIV.linux.org.uk> From: Linus Torvalds Date: Sun, 1 Jul 2018 13:25:20 -0700 Message-ID: Subject: Re: [git pull] vfs fixes To: Al Viro Cc: linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jul 1, 2018 at 1:05 PM Al Viro wrote: > > Point taken... Would something along the lines of "fixing a leak > introduced in procfs-seq_file series" be OK, or do you prefer > more details? That would have been sufficient. As it was now, it looked to all intents and purposes like adding a new function. So I went and looked what was going on, and found the "oh, fix a leak" and wrote my own merge message. But it's the kind of thing I would really want to just get in the pull request - an explanation of why I should pull. Linus