| 1 |
Pacho Ramos posted on Sun, 16 Jun 2013 15:19:26 +0200 as excerpted: |
| 2 |
|
| 3 |
> El dom, 16-06-2013 a las 12:42 +0000, Duncan escribió: |
| 4 |
>> Pacho Ramos posted on Sat, 15 Jun 2013 22:37:50 +0200 as excerpted: |
| 5 |
>> |
| 6 |
>> [Snipped as my comment refers to the subject] |
| 7 |
>> |
| 8 |
>> Could you split-up announcements like this into multiple announcements, |
| 9 |
>> so the subject lines remain a reasonable length, please? |
| 10 |
> |
| 11 |
> I am not sure it deserves the effort, or do you have any idea about how |
| 12 |
> to send all this in splitted mails easily (currently, I need to simply |
| 13 |
> add all the mask entry and copy it to the mail body) :/ |
| 14 |
|
| 15 |
If it's a (semi-)manual process as the "simply add all" seems to imply, |
| 16 |
you could just do it in smaller chunks, say no more than <arbitrary |
| 17 |
number, simply eyeballing it's fine> a half-dozen packages at a time, so |
| 18 |
the subject length stays reasonable. Or as I said if the packages are |
| 19 |
all related, don't worry about the length as it'd then be reasonably easy |
| 20 |
to glance at and say "oh, that's nothing I care about anyway" or "that |
| 21 |
interests me I better look closer". |
| 22 |
|
| 23 |
If it's an automated script, that could be more difficult, but at the |
| 24 |
same time, I'd /guess/ that if there's a script doing most of it already, |
| 25 |
adding logic to split by category and fire off one for each if there's |
| 26 |
more than a half-dozen individual packages to deal with at once, |
| 27 |
shouldn't be but an incremental add. |
| 28 |
|
| 29 |
Using this one as an example, by my count there's 20 packages listed, |
| 30 |
which would split into ~3-4 separate announcements using the eyeballed |
| 31 |
half-dozen method, or ~7 announcements using a crude group by first |
| 32 |
category-segment (rox-*(2), sys-*(2), media*(1), dev-*(4), gnome-*(2), |
| 33 |
net-*(5), app-*(3) ) automated method. Using an incrementally more |
| 34 |
advanced "combine groups until you hit a half-dozen max" method, rox/sys/ |
| 35 |
media would combine for one announcement, dev/gnome combine, net by |
| 36 |
itself, app by itself, four separate announcements total. |
| 37 |
|
| 38 |
If nobody else finds the long subjects worth worrying about, maybe it's |
| 39 |
just me and don't worry about it. But I'd think it'd be easier to follow |
| 40 |
threads just from an "I'll take this one" reply context as well, as even |
| 41 |
just that gets confusing to follow when there's 20 unrelated packages in |
| 42 |
the same thread, such that a dev interested in just one now has to look |
| 43 |
at all the replies to see if there's an "I'll take this" on his target |
| 44 |
package already, instead of just scanning subjects and seeing there isn't |
| 45 |
a reply yet to the thread naming the single package he's interested in. |
| 46 |
|
| 47 |
But maybe it /is/ just me... <shrug> |
| 48 |
|
| 49 |
-- |
| 50 |
Duncan - List replies preferred. No HTML msgs. |
| 51 |
"Every nonfree program has a lord, a master -- |
| 52 |
and if you use the program, he is your master." Richard Stallman |
Archives