public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, ...)
Date: Fri, 03 May 2013 13:25:03 -0400	[thread overview]
Message-ID: <20130503172503.GP15975@odin.tremily.us> (raw)
In-Reply-To: <20130410150909.GC4694@odin.tremily.us>

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

On Wed, Apr 10, 2013 at 11:09:09AM -0400, W. Trevor King wrote:
> On #gentoo-releng, Jorge asked for a list of of outstanding patches
> that have been cooking on the mailing list.

Three weeks later, these branches (sshd-tweak, xsession,
livecd-startx, releng-link, bugs) are all still open, and my new
binpkg-blacklist branch has been added to the queue:

  branch: binpkg-blacklist
  summary: spec: Add binpkg_blacklist option for troublesome packages
  http://mid.gmane.org/cover.1366137972.git.wking@tremily.us

    Work around broken binary package support, instead of using
    stage-level blacklists.

I thought I'd bump them again since things have quieted down, although
we still haven't had a new release…

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-05-03 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 20:27 [gentoo-catalyst] Newer releng spec files? W. Trevor King
2013-01-31 20:48 ` Dustin C. Hatch
2013-01-31 22:33   ` [gentoo-catalyst] [PATCH] examples/README: Add a pointer to the releng Git repository W. Trevor King
2013-03-02 20:22     ` [gentoo-catalyst] Bumping a few patches (releng-link, bugs, spec-comments, howto) W. Trevor King
2013-04-10 15:09       ` [gentoo-catalyst] " W. Trevor King
2013-05-03 17:25         ` W. Trevor King [this message]
2013-12-14  4:58         ` W. Trevor King
2013-12-20  5:02           ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, howto-stage-descriptions, ...) W. Trevor King
2013-12-31 17:03             ` W. Trevor King
2014-01-01  6:20               ` Jorge Manuel B. S. Vicetto
2014-01-01 17:54                 ` W. Trevor King
2014-01-06  3:55               ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, term-env-var, ...) W. Trevor King
2014-06-14 16:14                 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, pandoc-mediawiki, ...) W. Trevor King
2014-06-14 23:27                   ` Brian Dolbec
2014-06-15  0:04                     ` W. Trevor King
2014-06-15  1:01                       ` Brian Dolbec
2013-01-31 22:56   ` [gentoo-catalyst] Newer releng spec files? W. Trevor King
  -- strict thread matches above, loose matches on Subject: below --
2013-02-01  2:19 [gentoo-catalyst] [PATCH] examples: Add newlines to accidentally unwrapped comment lines W. Trevor King
2013-02-01  1:34 ` [gentoo-catalyst] [PATCH] Move bug-reporting and mailing list notes from TODO to README W. Trevor King

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=20130503172503.GP15975@odin.tremily.us \
    --to=wking@tremily.us \
    --cc=gentoo-catalyst@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