From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH] tile: support GENERIC_KERNEL_THREAD and GENERIC_KERNEL_EXECVE Date: Wed, 24 Oct 2012 02:56:13 +0100 Message-ID: <20121024015613.GB2616@ZenIV.linux.org.uk> References: <20121019213548.GR2616@ZenIV.linux.org.uk> <5082A1F1.3080303@tilera.com> <20121020153401.GT2616@ZenIV.linux.org.uk> <20121020171643.GU2616@ZenIV.linux.org.uk> <5086D432.4070008@tilera.com> <20121023184122.GZ2616@ZenIV.linux.org.uk> <20121023205119.GA27729@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Thomas Gleixner , Jeff King , Chris Metcalf , LKML , linux-arch@vger.kernel.org, Catalin Marinas , git@vger.kernel.org, Junio C Hamano To: Linus Torvalds X-From: linux-arch-owner@vger.kernel.org Wed Oct 24 03:56:34 2012 Return-path: Envelope-to: glka-linux-arch@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TQqCu-0005xm-UK for glka-linux-arch@plane.gmane.org; Wed, 24 Oct 2012 03:56:33 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932080Ab2JXB4Y (ORCPT ); Tue, 23 Oct 2012 21:56:24 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:33728 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755785Ab2JXB4X (ORCPT ); Tue, 23 Oct 2012 21:56:23 -0400 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.76 #1 (Red Hat Linux)) id 1TQqCb-0001Dj-9P; Wed, 24 Oct 2012 01:56:13 +0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-arch-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org Archived-At: On Wed, Oct 24, 2012 at 04:02:49AM +0300, Linus Torvalds wrote: > On Wed, Oct 24, 2012 at 12:25 AM, Thomas Gleixner wrote: > >> > >> It is spelled: > >> > >> git notes add -m 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 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...