public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item preceding net-print/cups-1.6 stabilization
Date: Sun, 30 Jun 2013 15:50:11 +0200	[thread overview]
Message-ID: <201306301550.17038.dilfridge@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

Am Samstag, 29. Juni 2013, 00:03:36 schrieb Andreas K. Huettel:
> See below, I'm grateful for any improvements.
> 
> As there is a pending security bug, I'd like to commit this news item on
> Sunday 2013/6/30 12:00 UTC and immediately afterwards request cups-1.6
> stabilization.
> 
> --

News item committed.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-06-30 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 13:50 Andreas K. Huettel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-06-28 22:03 [gentoo-dev] News item preceding net-print/cups-1.6 stabilization Andreas K. Huettel
2013-06-29 19:41 ` Luca Barbato
2013-06-29 21:47   ` Andreas K. Huettel
2013-07-05  6:49 ` James Cloos

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=201306301550.17038.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --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