From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Johan Herland <johan@herland.net>,
Junio C Hamano <gitster@pobox.com>,
ksummit-discuss@lists.linuxfoundation.org,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-discuss] [TOPIC] Metadata addendum to git commit
Date: Thu, 22 May 2014 09:49:44 +0200 [thread overview]
Message-ID: <CAMuHMdWmB-0dd7tC8cF-Aj=TOPO-D8nvUcjTUoVNAz-EBTVWaQ@mail.gmail.com> (raw)
In-Reply-To: <s5hy4xufe8q.wl%tiwai@suse.de>
On Thu, May 22, 2014 at 9:45 AM, Takashi Iwai <tiwai@suse.de> wrote:
>> Yes, unless you add it (using git-notes) as an annotation to the fix
>> commit, but then you're back to the (perceived) problem of sharing
>> those notes.
>>
>> Alternatively, you would have to find a different mechanism for
>> developers to insert entries into their reverse mappings from
>> post-facto/missing "Fixes:" tags.
>
> After reconsidering this, now I don't think we can rely only on Fixes
> tag. The addendum notes are useful for other purposes, e.g. finding
> external links. And, yet one useful thing by addendum is that you can
> mark the regression no matter whether it's already fixed or not. With
> Fixes-tag reverse mapping, you can find only fixed regressions, but
> not open regressions.
Do you want to import the whole bug tracking system, too? ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2014-05-22 7:49 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
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 [this message]
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='CAMuHMdWmB-0dd7tC8cF-Aj=TOPO-D8nvUcjTUoVNAz-EBTVWaQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=gitster@pobox.com \
--cc=jason@lakedaemon.net \
--cc=johan@herland.net \
--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