Markus Neteler wrote:
I have taken liverty to change that. Now trac posts as:
from GRASS trac <trac@osgeo.org> <<- changed sender
reply-to grass-dev@lists.osgeo.org,
to undisclosed-recipients,
date Sun, Apr 13, 2008 at 9:05 PM
subject Re: [GRASS trac] #90: v.parallel: problems with inside
corners <<- changed prefix
mailed-by osgeo.org
Hope that's better.
Not in any meaningful sense. It still doesn't tell me who made the
comment, or where it fits in relation to the rest of the thread.
E.g. compare:
40 R Martin Landa Mar 20 16/485 "[GRASS-dev] g.mapsets, print only accessible mapsets"
41 Markus Neteler Mar 20 44/1219 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
42 Martin Landa Mar 20 28/1011 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
43 Maris Nartiss Mar 20 23/639 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
44 Hamish Mar 20 27/866 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
45 Martin Landa Mar 20 29/880 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
46 Glynn Clements Mar 20 26/912 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
47 R Martin Landa Mar 20 37/1427 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
48 Glynn Clements Mar 21 53/2146 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
49 R Martin Landa Mar 24 124/5368 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
50 Glynn Clements Mar 24 33/1157 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
51 R Martin Landa Mar 24 92/5354 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
52 Glynn Clements Mar 25 21/749 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
53 Martin Landa Mar 25 23/779 "Re: [GRASS-dev] g.mapsets, print only accessible mapsets"
to:
631 GRASS GIS Apr 4 33/1722 "[GRASS-dev] [GRASS GIS] #117: r.digit fails if launched from menu"
632 GRASS GIS Apr 4 33/1718 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
633 GRASS GIS Apr 5 30/1495 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
634 GRASS GIS Apr 5 32/1653 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
635 GRASS GIS Apr 5 44/2597 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
637 GRASS GIS Apr 5 34/1795 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
638 GRASS GIS Apr 5 36/1929 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
639 GRASS GIS Apr 6 53/3230 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
641 GRASS GIS Apr 7 39/2200 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
642 GRASS GIS Apr 12 30/1491 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit fails if launched from menu"
643 GRASS GIS Apr 13 50/2987 "[GRASS-dev] Re: [GRASS GIS] #117: r.digit: make guarantee_xmon fail nicely on WinGrass"
Also: a follow-up results in "GRASS GIS wrote:", and I have to
actually think about trimming the message to indicate who is being
replied to.
Also, having both [GRASS-dev] and [GRASS trac] in the subject line
wastes even more space that could be used for meaningful information.
I accept that we are probably stuck with [GRASS-dev] as a sop to OE
users (any decent mail client can filter on the Sender: field, and so
doesn't need Subject: to be mangled), but the second one is pointless.
These factors (coupled with the fact that I have to switch away from
the XEmacs window where I spend 99% of my time to a web browser) make
trac sufficiently inferior to email that I don't intend to use it for
discussion, and will probably pay less attention to trac-based threads
than those where I can actually navigate the thread.
--
Glynn Clements <glynn@gclements.plus.com>