[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121024015613.GB2616@ZenIV.linux.org.uk>
Date: Wed, 24 Oct 2012 02:56:13 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Jeff King <peff@...f.net>,
Chris Metcalf <cmetcalf@...era.com>,
LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>, git@...r.kernel.org,
Junio C Hamano <gitster@...ox.com>
Subject: Re: [PATCH] tile: support GENERIC_KERNEL_THREAD and
GENERIC_KERNEL_EXECVE
On Wed, Oct 24, 2012 at 04:02:49AM +0300, Linus Torvalds wrote:
> On Wed, Oct 24, 2012 at 12:25 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> >>
> >> It is spelled:
> >>
> >> git notes add -m <comment> SHA1
> >
> > Cool!
>
> Don't use them for anything global.
>
> Use them for local codeflow, but don't expect them to be distributed.
> It's a separate "flow", and while it *can* be distributed, it's not
> going to be for the kernel, for example. So no, don't start using this
> to ack things, because the acks *will* get lost.
How about git commit --allow-empty, with
"belated ACK for <commit>
Acked-by: <...>
" as commit message? I mean, that ought to work and propagate sanely,
but I'm really not sure if that's something in a good taste and should
be allowed as a common practice...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists