From: Li Zefan <lizefan@huawei.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Metadata addendum to git commit
Date: Wed, 14 May 2014 09:40:41 +0800 [thread overview]
Message-ID: <5372C999.6070401@huawei.com> (raw)
In-Reply-To: <s5hvbt9izdm.wl%tiwai@suse.de>
On 2014/5/13 21:25, Takashi Iwai wrote:
> 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.
>
Yeah, this is very useful.
For example, instead of adding a tag in the changelog to point to
the guilt commit that introduces the bug:
Fixes: commit_id ("Subject")
It's much more convenient and useful if we can add metadata to the
guilt commit that points to later fixes, and then we simply ask
git to show us those fixes. This helps a lot to people who need to
backport things to older kernels.
> 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.
>
next prev parent reply other threads:[~2014-05-14 1:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 13:25 Takashi Iwai
2014-05-13 23:23 ` NeilBrown
2014-05-13 23:29 ` Jiri Kosina
2014-05-13 23:49 ` NeilBrown
2014-05-14 1:40 ` Li Zefan [this message]
2014-05-16 3:07 ` Jason Cooper
2014-05-16 5:12 ` Christian Couder
2014-05-16 9:24 ` Li Zefan
2014-05-16 9:33 ` Takashi Iwai
2014-05-18 19:23 ` Christian Couder
2014-05-18 22:12 ` Jason Cooper
2014-05-19 6:34 ` Christian Couder
2014-05-19 13:29 ` Takashi Iwai
2014-05-20 6:37 ` Christian Couder
2014-05-20 7:06 ` Takashi Iwai
2014-05-21 5:36 ` Christian Couder
2014-05-22 4:49 ` Christian Couder
2014-05-22 5:58 ` Takashi Iwai
2014-05-22 6:28 ` Johan Herland
2014-05-22 6:52 ` Christian Couder
2014-05-22 7:29 ` Johan Herland
2014-05-22 7:45 ` Takashi Iwai
2014-05-22 7:49 ` Geert Uytterhoeven
2014-05-22 8:03 ` Takashi Iwai
2014-05-22 15:51 ` Theodore Ts'o
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=5372C999.6070401@huawei.com \
--to=lizefan@huawei.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tiwai@suse.de \
/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