all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: The fixes-bug field
Date: Thu, 16 Jan 2014 18:22:52 +0100	[thread overview]
Message-ID: <87fvon4z9v.fsf@Rainer.invalid> (raw)
In-Reply-To: 20140116163011.GC17303@thyrsus.com

Eric S. Raymond writes:
> Stefan Monnier <monnier@iro.umontreal.ca>:
>> > TL;DR: Possible, but a serious PITA.  If this is just an It Would Be Nice
>> > rather than being key to an established workflow I'd rather not go there.
>> 
>> The "fixes" info is important.  Not just "would be nice".
>> Maybe there are other ways to preserve it (e.g. "bzr log", collect the
>> "Fixes" notes and then pass them to "git notes" somehow).
>> 
>> Which format is used to keep the "fixes" info in the Git repository is
>> not terribly important, but the info should appear in the "git
>> log" output.
>
> OK, I'll come up with something.

Even with the doubts of what might happen to Git notes in the long run,
I'd think Emacs should have a notes tree (refs/notes/key-value perhaps)
that is used as a key/value store, not for amending commit messages.
Besides the "fixes" stuff maybe the Hydra build results could be stored
there so that when bisecting one could skip over broken commits
automatically.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html




  parent reply	other threads:[~2014-01-16 17:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 14:13 The fixes-bug field Eric S. Raymond
2014-01-16 16:13 ` Stefan Monnier
2014-01-16 16:30   ` Eric S. Raymond
2014-01-16 16:55     ` Eli Zaretskii
2014-01-16 17:54       ` Glenn Morris
2014-01-16 18:09         ` Eric S. Raymond
2014-01-16 18:38         ` Darren Hoo
2014-01-16 19:32           ` Stefan Monnier
2014-01-16 20:06             ` Glenn Morris
2014-01-16 21:30               ` Eli Zaretskii
2014-01-16 21:24           ` Eli Zaretskii
2014-01-16 18:55         ` Paul Eggert
2014-01-16 19:13           ` Glenn Morris
2014-01-16 20:25             ` Paul Eggert
2014-01-16 18:08       ` Eric S. Raymond
2014-01-16 18:36         ` Eli Zaretskii
2014-01-16 20:04           ` Eric S. Raymond
2014-01-16 21:29             ` Eli Zaretskii
2014-01-16 21:47               ` Eric S. Raymond
2014-01-17  7:32                 ` Eli Zaretskii
2014-01-17  7:58                   ` Paul Eggert
2014-01-17  8:04                     ` Jarek Czekalski
2014-01-17  9:21                       ` Yuri Khan
2014-01-17 14:31                     ` Stefan Monnier
2014-01-17 15:57                       ` Lars Ingebrigtsen
2014-01-17 16:12                         ` Stefan Monnier
2014-01-17 17:20                           ` Lars Ingebrigtsen
2014-01-18  9:19                         ` Jarek Czekalski
2014-01-18 16:02                           ` Lars Ingebrigtsen
2014-01-17 13:16                   ` Eric S. Raymond
2014-01-17 13:55                     ` Eli Zaretskii
2014-01-17 14:26                   ` Stefan Monnier
2014-01-16 17:00     ` Glenn Morris
2014-01-16 17:22     ` Achim Gratz [this message]
2014-01-16 17:57       ` Glenn Morris
  -- strict thread matches above, loose matches on Subject: below --
2014-01-16 14:15 Eric S. Raymond
2014-01-16 17:11 ` Eli Zaretskii
2014-01-17 20:29   ` Eric S. Raymond
2014-01-18  7:51     ` Eli Zaretskii

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=87fvon4z9v.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.