After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 694066 - Customizable attribution string
Customizable attribution string
Status: RESOLVED DUPLICATE of bug 496348
Product: evolution
Classification: Applications
Component: Mailer
3.18.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-02-18 08:05 UTC by Severo Raz
Modified: 2015-10-06 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Severo Raz 2013-02-18 08:05:48 UTC
The attribution string that appears on top of quoted text should be customizable. I don't think a GUI is necessary for it, a dconf key would do just fine since this is not something everybody wants to customize.
Comment 1 André Klapper 2013-07-01 09:09:20 UTC
Sounds like bug 210577.

*** This bug has been marked as a duplicate of bug 210577 ***
Comment 2 Severo Raz 2013-07-01 23:34:22 UTC
Sorry I don't see how these two point to the same issue, what if you wanted to format the message attribution string with a language-less format? Something like 

2013-07-01 T09:09:20 UTC André:
Comment 3 Severo Raz 2015-09-27 12:46:43 UTC
(In reply to André Klapper from comment #1)
> Sounds like bug 210577.
> 
> *** This bug has been marked as a duplicate of bug 210577 ***

(In reply to Severo Raz from comment #2)
> Sorry I don't see how these two point to the same issue, what if you wanted
> to format the message attribution string with a language-less format?
> Something like 
> 
> 2013-07-01 T09:09:20 UTC André:

André can you reopen this bug?
Comment 4 Severo Raz 2015-10-06 13:37:12 UTC
I have looked on further an it seems this is a *very* recurrent bug report. The initial report seems to be bug #496348. I will mark this bug as duplicate.

*** This bug has been marked as a duplicate of bug 496348 ***