All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>,
	David Gibson
	<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	"Yann E. MORIN" <yann.morin.1998-GANU6spQydw@public.gmane.org>
Subject: Re: RFC: New release for DTC?
Date: Thu, 30 May 2013 11:45:23 -0600	[thread overview]
Message-ID: <51A79033.7080800@wwwdotorg.org> (raw)
In-Reply-To: <201208232015.39613.yann.morin.1998-GANU6spQydw@public.gmane.org>

On 08/23/2012 12:15 PM, Yann E. MORIN wrote:
> Hello All!
> 
> Following advice from Jon Loeliger, I would suggest that a new release
> of DTC be tagged and packaged.
> 
> It is important for some projects to rely on a released version, rather
> than use a random cset from the repository. Comes to mind, the automated
> build-systems, such as buildroot.
> 
> Of course, I can help, if need be! ;-)
> 
> Are there any others who think that a release would make sense?

I'd love to see a new release. This would for example allow the U-Boot
project to say "dtc vXXX is required to build the DT files contained in
U-Boot", which might make agreeing on allowing the use of new dtc
features in U-Boot easier. While this could simply be done by referring
to a specific git commit ID, release versions or tags probably carry
more weight. Tagging a release might also act as a specific trigger for
distros to pick up and carry the new version.

Does it make sense to simply tag the current git HEAD as v1.4? If so,
can we do this?

  parent reply	other threads:[~2013-05-30 17:45 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
     [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 [this message]
     [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=51A79033.7080800@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jdl-CYoMK+44s/E@public.gmane.org \
    --cc=yann.morin.1998-GANU6spQydw@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.