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