From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Dave Abrahams <dave@boostpro.com>, 11318@debbugs.gnu.org
Subject: bug#11318: [Patchset] A bugfix and an arguable bugfix for ediff-inferior-compare-regions
Date: Sat, 12 May 2012 13:18:45 -0400 [thread overview]
Message-ID: <jwv4nrl4914.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <36k40kd5vv.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 10 May 2012 00:20:04 -0400")
>> Arguably, debbugs (sh|c)ould pay attention to the References: (or
>> In-reply-to:) header to automatically put the replies in the same bug as
>> their "parent" message.
> It does (I added this feature), but:
Good, thanks. I did remember you adding such a thing, but I figured it
must have been something slightly different.
> a) It needs time (I think) to process the first message and update the
> bug index with the message-id, so if all messages arrive at the same
> instant, it doesn't work.
Oh, yes, that's a real bummer. So we'd have to sequentialize processing
of incoming messages (if it's not done yet) and handle the message-ids
both ways: i.e. recognize when a message comes after its reply and put
it in the same bug-id. That could be tricky/risky indeed.
> b) I made the decision to require a subject starting with "Re:" for this
> to take effect, because sometimes people reply to an old message and
> change the subject with the intention of creating a new report.
> (I'm pretty sure I've said this before.)
> I'm feeling like I should admit defeat on this aspect, since it seems
> people just love messing around with the subject header.
Is there an easy way to see (in retrospect) whether this "Re:" filtering
did the right thing more often than not?
> I also added something that makes [patch] equivalent to
> Tags:patch
Great, tho it doesn't seem to be used much.
Stefan
next prev parent reply other threads:[~2012-05-12 17:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 19:28 bug#11318: [Patchset] A bugfix and an arguable bugfix for ediff-inferior-compare-regions Dave Abrahams
2012-04-23 19:28 ` bug#11319: [PATCH 1/2] BUGFIX: select current-diff-comparison regions for ediff-inferior-compare-regions correctly Dave Abrahams
2012-12-14 15:23 ` Stefan Monnier
2012-12-14 17:17 ` Dave Abrahams
[not found] ` <e5472cbf85e944178dd2aebb9d6ed40a@HUBCAS1.cs.stonybrook.edu>
2012-12-15 4:46 ` Michael Kifer
2012-12-17 23:22 ` Dave Abrahams
2012-12-17 23:28 ` Michael Kifer
2012-12-17 23:44 ` Dave Abrahams
2012-12-18 0:01 ` Michael Kifer
2012-04-23 19:28 ` bug#11320: [PATCH 2/2] Useful behavior for ediff-inferior-compare-regions when merging with an ancestor Dave Abrahams
2018-05-12 2:03 ` Noam Postavsky
2018-06-29 2:13 ` Noam Postavsky
2012-05-10 1:05 ` bug#11318: [Patchset] A bugfix and an arguable bugfix for ediff-inferior-compare-regions Glenn Morris
2012-05-10 1:40 ` Dave Abrahams
2012-05-10 4:04 ` Stefan Monnier
2012-05-10 4:20 ` Glenn Morris
2012-05-12 17:18 ` Stefan Monnier [this message]
2012-07-21 2:30 ` Dave Abrahams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4nrl4914.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11318@debbugs.gnu.org \
--cc=dave@boostpro.com \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).