[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: DnD mail into thread
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-08-10 18:47:58
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday, 10. August 2001 11:43, Wolfgang Rohdewald wrote:
> I'd love being able telling kmail that some mail belongs to a certain
> thread.
>
> Idea: DnD one or several mails to another mail. This adds an
> In-Reply-To header to the first mail pointing to that other mail.
> Maybe there should be a question "do you really want to put the
> selected mails into thread "blablalbal" ?" with an option to suppress
> that question.
>
> Would that be feasible? Should I open a wishlist item or would it be
> closed again right away?

Maybe there is already a wishlist item for this. If not feel free to 
submit one. At least I won't close it right away because I also have 
thought about something like this some time ago.
But, adding an In-Reply-To header isn't such a good idea because the 
message would have to be copied at the end of the file corresponding to 
the folder (at least if the folder is in mbox format). It would be 
easier to add some kind of pointer to the index file. The disadvantage 
of this is that this information will be lost if the index file has to 
be rebuild for some reason.

> Also, it would be nice if the kde bug messages (like "marked as
> done") had an In-Reply-To header referencing the original bug report.

This is slightly OT, isn't it?
You should send this wish to the guy who is responsible for the bug 
report system. Unfortunately I currently don't know who it is. Maybe 
Daniel Naber? Or coolo?
BTW, currently the In-Reply-To header references the message which was 
sent to the bug report system to close this bug report via a message to 
#-done@bugs.kde.org. This shouldn't be changed.
If OTOH the bug report was closed via a message to control@bugs.kde.org 
then making the In-Reply-To header reference the original bug report 
would be a good idea.

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7dCxeGnR+RTDgudgRAjvfAJ97z93GWe9o58V/pXrfxuFwe8rqlwCgmhjt
zUnLKE0ZHAWusMGqpBjQwDA=
=a/wR
-----END PGP SIGNATURE-----
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]