Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc-admins post from martin@barkynet.com requires approval
Date: Wed, 2 Dec 2015 17:00:28 -0500	[thread overview]
Message-ID: <20151202220028.GG23754@vapier.lan> (raw)
In-Reply-To: <878u5cfs82.fsf@dell.be.48ers.dk>

On 02 Dec 2015 22:36, Peter Korsgaard wrote:
> >>>>> "Bernhard" == Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> writes:
> 
>  >> From: Martin Bark <martin@barkynet.com>
>  >> Cc:
>  >> Date: Wed, 2 Dec 2015 20:07:13 +0000
>  >> Subject: 2015.11 missing from version field
>  >> Hi,
>  >> 
>  >> Can you please add 2015.11 to the version field in bugzilla.
> 
>  > Done. I'd prefer if you could ask the buildroot folks directly next time.
> 
> Yes, me too. I normally remember to add the releases, but this time I
> forgot.

i've added a bugzilla component, but not sure that'll really help smooth
over this scenario.  i looked at the API available, but i'm not seeing a
callback to update the versions list.
	https://www.bugzilla.org/docs/4.4/en/html/api/

there is one to get the current list:
	https://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService/Product.html

maybe the buildroot release scripts can print a reminder ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151202/85f18ca6/attachment.asc>

  reply	other threads:[~2015-12-02 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2362.1449086836.25824.uclibc-admins@busybox.net>
2015-12-02 20:29 ` [Buildroot] uClibc-admins post from martin@barkynet.com requires approval Bernhard Reutner-Fischer
2015-12-02 21:36   ` Peter Korsgaard
2015-12-02 22:00     ` Mike Frysinger [this message]
2015-12-02 22:59       ` Peter Korsgaard
2015-12-02 23:31         ` Mike Frysinger
2016-02-02  8:15           ` Mike Frysinger

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=20151202220028.GG23754@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=buildroot@busybox.net \
    /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