From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: Robert Schwebel <r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Device Tree Mailing List
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Next formal dtc release?
Date: Fri, 06 May 2011 08:46:39 -0500 [thread overview]
Message-ID: <E1QILMd-0008Db-VP@jdl.com> (raw)
In-Reply-To: <20110505065559.GX3811-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> > Because we have a pretty thorough testsuite, the current tip is nearly
> > always suitable for release. That's one of the reasons we frequently
> > forget to get around to doing a formal release.
>
> any news about a release?
I am out of sorts Saturday, but I will try to do it Sunday.
I have one "tested, it works" confirmation so far. Others?
I'm positing of a 1.3.0 release number for it.
jdl
next prev parent reply other threads:[~2011-05-06 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 1:26 Next formal dtc release? David VomLehn
[not found] ` <20110420012610.GA6895-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2011-04-20 2:37 ` Grant Likely
[not found] ` <BANLkTi=JxBUEUGq_b+8w5c+LYq9-dKV+Bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-20 3:19 ` Jon Loeliger
[not found] ` <E1QCNwx-0003YA-Pv-CYoMK+44s/E@public.gmane.org>
2011-04-20 22:14 ` David VomLehn
[not found] ` <20110420221426.GA18409-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2011-04-21 1:41 ` David Gibson
2011-05-05 6:55 ` Robert Schwebel
[not found] ` <20110505065559.GX3811-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-05-06 13:46 ` Jon Loeliger [this message]
[not found] ` <E1QILMd-0008Db-VP-CYoMK+44s/E@public.gmane.org>
2011-05-08 20:11 ` Jon Loeliger
[not found] ` <E1QJAKI-0007c1-RV-CYoMK+44s/E@public.gmane.org>
2011-05-09 8:23 ` Robert Schwebel
2011-05-09 20:32 ` Tabi Timur-B04825
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=E1QILMd-0008Db-VP@jdl.com \
--to=jdl-cyomk+44s/e@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.