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 12:42:44 +0000 (UTC)	[thread overview]
Message-ID: <pan$e2e44$b9c7d910$9cc2c072$26d9f2f5@cox.net> (raw)
In-Reply-To: 1371328670.17293.9.camel@localhost

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?

Particularly when there's lots of unrelated packages.  If they're all in 
the same pkg-category or are otherwise obviously related, it's not so 
bad.  But here we have rox packages, firmware, cluster, media, office, 
gnome, dev-sharp... all combined in the same very long subject that's 
well beyond any reasonable single-line subject length, making it very 
easy to miss something critical for the very people who are otherwise 
targeted, those who could be interested in maintaining those packages, as 
well as any remaining users who might like an early heads-up before they 
find their @world update broken due to now-masked packages that they'd 
have otherwise caught in the last-rites announcement.

That request made, thanks for helping to de-cruft the tree.  I'm glad 
someone's putting in the effort. =:^)

-- 
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



  parent reply	other threads:[~2013-06-16 12:43 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 ` Duncan [this message]
2013-06-16 13:19   ` [gentoo-dev] " Pacho Ramos
2013-06-16 14:09     ` Duncan
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$e2e44$b9c7d910$9cc2c072$26d9f2f5@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