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: News item review: SquashDelta syncing support
Date: Sun, 17 May 2015 08:52:39 +0000 (UTC)	[thread overview]
Message-ID: <pan$2eca3$bd189996$39a65744$9883e181@cox.net> (raw)
In-Reply-To: 20150517054715.7ef8bcc4@pomiot.lan

Michał Górny posted on Sun, 17 May 2015 05:47:15 +0200 as excerpted:

> Dnia 2015-05-16, o godz. 20:38:36 Michael Orlitzky <mjo@gentoo.org>
> napisał(a):
> 
>> On 05/16/2015 06:01 PM, Michał Górny wrote:
>> >>
>> >> We have gentoo-announce@g.o and gentoo-user@g.o too!
>> > 
>> > That's gentoo-dev-announce. 'dev' is the key part. And gentoo-user@
>> > is doubtedly used by sysadmins.
>> > 
>> > 
>> This one:
>> 
>> https://archives.gentoo.org/gentoo-announce/
> 
> First time I hear about it. Looks to be used primarily for GLSAs.
> I wonder if anyone actually uses it.

Answering the "does anyone actually use it" bit...

I'm subscribed (via gmane) and scan new message subjects, at least, 
reading messages when they (might) pertain.

Tho the GLSAs are of questionable usefulness here, since I'm on ~arch and 
update regularly enough that announced affected versions are usually 
ancient history on my boxen.  I think I've actually seen one or two that 
applied to me... in over a decade on gentoo.

But I still subscribe and at least scan titles, as for me it's part of 
being a good admin, just in case, both for the GLSAs, and in case there's 
anything else of importance posted.

Of course if the announce list was actually used for announcements other 
than GLSAs, it'd definitely enhance its general usefulness.  So please do 
start announcing stuff there -- IMO, anything fit for the front page is 
fit for the general announce list as well! =:^)

-- 
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:[~2015-05-17  8:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 14:51 [gentoo-dev] News item review: SquashDelta syncing support Michał Górny
2015-05-15 15:23 ` Dirkjan Ochtman
2015-05-15 16:15   ` Diamond
2015-05-15 18:32     ` Ian Stakenvicius
2015-05-15 19:33       ` Rich Freeman
2015-05-15 19:38         ` Ian Stakenvicius
2015-05-18  5:48         ` [gentoo-dev] " Martin Vaeth
2015-05-18  6:10           ` Brian Dolbec
2015-05-19  6:36             ` Martin Vaeth
2015-05-16 21:59   ` [gentoo-dev] " Michał Górny
2015-05-16 14:59 ` Michael Orlitzky
2015-05-16 18:38   ` Alexis Ballier
2015-05-16 19:18     ` Pacho Ramos
2015-05-16 19:23       ` Michael Orlitzky
2015-05-16 20:34         ` Brian Dolbec
2015-05-16 22:01         ` Michał Górny
2015-05-17  0:38           ` Michael Orlitzky
2015-05-17  3:47             ` Michał Górny
2015-05-17  8:52               ` Duncan [this message]
2015-05-17 18:52               ` Dale
2015-05-17 19:41               ` Michael Orlitzky
2015-05-20  7:56               ` Marc Schiffbauer
2015-05-16 22:00   ` Michał Górny
2015-05-17  0:45     ` Michael Orlitzky
2015-05-17  8:41       ` [gentoo-dev] " Duncan
2015-05-17 13:51     ` [gentoo-dev] " Ciaran McCreesh
2015-05-16 20:48 ` Alon Bar-Lev
2015-05-16 22:06   ` Michał Górny

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$2eca3$bd189996$39a65744$9883e181@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