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