linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] aush^H^Hdit queue
Date: Tue, 17 Jan 2012 16:21:11 -0800	[thread overview]
Message-ID: <CA+55aFw_9Wm=qUH+39wb7Xq5KFTZZ4TqgkwMksrD_Q8G-uO3jg@mail.gmail.com> (raw)
In-Reply-To: <20120117213429.GS23916@ZenIV.linux.org.uk>

On Tue, Jan 17, 2012 at 1:34 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>        By all rights it's Eric's stuff; I hadn't got around to resurrecting
> audit.git until the end of December and this is what was in his tree (minus
> a couple of things obsoleted by Miklos' "fsnotify: don't BUG in
> fsnotify_destroy_mark()").  Please, pull from
> git://git.kernel.org:/pub/scm/linux/kernel/git/viro/audit.git for-linus

Ugh.

You have an extra colon there in that git tree address. Please fix your script.

But even more annoyingly, this is from the "help text" for one of the
new options:

  The config option toggles if a task setting it's loginuid requires
  CAP_SYS_AUDITCONTROL or if that task should require no special permissions
  but should instead only allow setting its loginuid if it was never
  previously set.  On systems which use systemd or a similar central
  ...

Christ people. It's/its. One is a contraction of "it is" (or "it
has"), the other is the genitive (aka possessive form) of "it".

Yeah, I'm sensitive. It hurts my head.

              Linus

  reply	other threads:[~2012-01-18  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 21:34 [git pull] aush^H^Hdit queue Al Viro
2012-01-18  0:21 ` Linus Torvalds [this message]
2012-01-18  0:38   ` Al Viro
2012-01-18  0:44     ` Linus Torvalds
2012-01-18  0:45     ` Al Viro
2012-01-18  0:47       ` Al Viro

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='CA+55aFw_9Wm=qUH+39wb7Xq5KFTZZ4TqgkwMksrD_Q8G-uO3jg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@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).