public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Lastrites: rox-base/rox-clib, sys-firmware/iwl3945-ucode, rox-extra/downloadmanager, sys-cluster/mpi-dotnet, media-tv/livestation, dev-lang/boo, gnome-extra/contacts, net-im/qutecom, net-fs/djmount, dev-python/gtkhtml-python, =gnome-extra/gtkhtml-2.11.1, app-office/osmo,app-office/taxbird,app-editors/fte, dev-util/monodoc, dev-dotnet/njb-sharp,net-wireless/ipw3945, net-wireless/ipw3945-ucode, net-wireless/ipw3945d
Date: Sun, 16 Jun 2013 14:09:38 +0000 (UTC)	[thread overview]
Message-ID: <pan$1ae91$1ee070ee$b32b432a$eb57593b@cox.net> (raw)
In-Reply-To: 1371388766.22480.2.camel@localhost

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



  reply	other threads:[~2013-06-16 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 20:37 [gentoo-dev] Lastrites: rox-base/rox-clib, sys-firmware/iwl3945-ucode, rox-extra/downloadmanager, sys-cluster/mpi-dotnet, media-tv/livestation, dev-lang/boo, gnome-extra/contacts, net-im/qutecom, net-fs/djmount, dev-python/gtkhtml-python, =gnome-extra/gtkhtml-2.11.1, app-office/osmo,app-office/taxbird,app-editors/fte, dev-util/monodoc, dev-dotnet/njb-sharp,net-wireless/ipw3945, net-wireless/ipw3945-ucode, net-wireless/ipw3945d Pacho Ramos
2013-06-16  3:38 ` [gentoo-dev] Re: [gentoo-dev-announce] " Patrick Lauer
2013-06-16  8:10   ` Pacho Ramos
2013-06-16 12:42 ` [gentoo-dev] " Duncan
2013-06-16 13:19   ` Pacho Ramos
2013-06-16 14:09     ` Duncan [this message]
2013-06-16 14:38       ` Pacho Ramos
2013-06-16 14:40       ` Pacho Ramos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$1ae91$1ee070ee$b32b432a$eb57593b@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox