From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: RFC: New release for DTC?
Date: Tue, 11 Dec 2012 08:55:17 -0600 [thread overview]
Message-ID: <E1TiREr-0004Mk-IP@jdl.com> (raw)
In-Reply-To: <CAPnjgZ23ofzihzCMb-i6NMDFuMrYabfo2JGeSPKz+E3gzqDnLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> >> >
> >> > This has been a bit of a perrenial problem. dtc development has been
> >> > sufficiently gradual that there haven't been many obvious points for
> >> > making new releases. dtc developers (i.e. Jon and my, mostly) don't
> >> > feel much pain from the lack of releases, since the git snapshots
> >> > generally work well (thanks to limited scope and a good testsuite).
> >> >
> >> > I wonder if we should move to a model of just making a release every 3
> >> > or 6 months from whatever happens to be in the tree at the time
> >> > (barring obvious known breakage, of course).
> >>
> >> yes please. even just a version that uses datestamps would be fine.
> >> -mike
> >
> > Fine by me.
>
> So is this happening? I agree a regular release would be useful, and I
> think it has been about 18 months since the last release.
I'll apply a couple 3 outstanding patches (from Kim Phillips)
and get around to tagging a new release. If you, or anyone else
have patches or functionality you want in this release, please
post those patches now.
jdl
next prev parent reply other threads:[~2012-12-11 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 18:15 RFC: New release for DTC? Yann E. MORIN
[not found] ` <201208232015.39613.yann.morin.1998-GANU6spQydw@public.gmane.org>
2012-08-24 1:36 ` David Gibson
[not found] ` <20120824013625.GA8067-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-11-17 17:50 ` Mike Frysinger
[not found] ` <201211171250.08597.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-11-18 0:00 ` Grant Likely
2012-12-10 22:40 ` Simon Glass
[not found] ` <CAPnjgZ23ofzihzCMb-i6NMDFuMrYabfo2JGeSPKz+E3gzqDnLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-11 14:55 ` Jon Loeliger [this message]
[not found] ` <E1TiREr-0004Mk-IP-CYoMK+44s/E@public.gmane.org>
2012-12-11 18:59 ` Simon Glass
2013-05-30 17:45 ` Stephen Warren
[not found] ` <51A79033.7080800-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-15 0:17 ` Grant Likely
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=E1TiREr-0004Mk-IP@jdl.com \
--to=jdl-cyomk+44s/e@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).