From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 8C4A598F for ; Tue, 13 May 2014 13:25:59 +0000 (UTC) Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1C35D201B4 for ; Tue, 13 May 2014 13:25:59 +0000 (UTC) Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id CBE6DAC46 for ; Tue, 13 May 2014 13:25:57 +0000 (UTC) Date: Tue, 13 May 2014 15:25:57 +0200 Message-ID: From: Takashi Iwai To: ksummit-discuss@lists.linuxfoundation.org MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: [Ksummit-discuss] [TOPIC] Metadata addendum to git commit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , I think this has been already raised a few times, but I'm still dreaming one thing in our git management: having some metadata collection / link for each commit. I don't mean for a thing like post-commit sign-off, but rather for tracking the information that has been revealed after commit, e.g. a regression the commit causes, the later fix commit, or a bugzilla or ML link for the further discussion or debugging session. The regression markers would be especially helpful to avoid a pitfall through performing bisection. IMO, it would be convenient if such information can be embedded in the published git tree, something like (infamous) git-notes. But, I'd like to hear any other options as well. thanks, Takashi