linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] VFS - the first pile
Date: Tue, 15 Mar 2011 23:02:10 +0100	[thread overview]
Message-ID: <20110315220210.GA8375@merkur.ravnborg.org> (raw)
In-Reply-To: <20110315213248.GL22723@ZenIV.linux.org.uk>

Hi Al.

> Shortlog:
> Al Viro (45):
>       compat breakage in preadv() and pwritev()
>       fix race in audit_get_nd()
>       kill path_lookup()
....

It would be nice if you could start to prefix your
changelog message with the sub-system they touch.

In an attempt to try to use the language you understand...

Why the hell do you continue making it so freaking difficult
to see what sub-system your patchs touches.
All sane thinking persons has long since learned to prefix their
changelogs with for example "vfs: bla bla" so sane humans
has a chance to realize what they touches.
You could probarly do better than this :-)

	Sam

  reply	other threads:[~2011-03-15 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 21:32 [git pull] VFS - the first pile Al Viro
2011-03-15 22:02 ` Sam Ravnborg [this message]
2011-03-15 22:18 ` Al Viro
2011-03-15 22:47   ` Linus Torvalds
2011-03-15 23:02     ` Al Viro
2011-03-16  6:19 ` Dave Chinner
2011-03-16  6:51   ` Al Viro
2011-03-16  7:21     ` Al Viro
2011-03-16 11:46       ` Theodore Tso
2011-03-16 13:07         ` Christoph Hellwig
2011-03-16 13:15           ` Al Viro
2011-03-16 13:18             ` Christoph Hellwig
2011-03-16 13:05 ` Christoph Hellwig
2011-03-16 13:10   ` Christoph Hellwig

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=20110315220210.GA8375@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).