linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: DTC 1.0.0 Release Coming?
Date: Thu, 26 Jul 2007 13:05:50 +1000	[thread overview]
Message-ID: <20070726030550.GA1149@localhost.localdomain> (raw)
In-Reply-To: <E1IDjSy-0003eC-T4@jdl.com>

On Wed, Jul 25, 2007 at 11:12:00AM -0500, Jon Loeliger wrote:
> Folks,
> 
> I'd like to make an official DTC Version 1.0.0 release soon!
> To that end, I've published a repo on jdl.com with a v1.0.0-rc1
> tag on it.  I anticipate some updates to the Documentation before
> a final 1.0.0 release still.  However, if you have something
> you would like to have be in The Real 1.0.0 release, please
> let me know soon!

It would certainly be great to have a release, since dtc is becoming
necessary for more and more kernel builds.

Only thing I'm not really happy with in the current release is the
versioning stuff.  For starters, it always reports my builds as
-dirty, even when they're not.  It also seems a bit hideously
complicated for what it does.  I'd prefer to see something simpler
using git-describe to derive the version strings directly from the git
tags themselves.  Obviously we need some sort of cacheing mechanism to
make the versioning work for tarball releases without the git history,
but I think we can handle that with a suitable "make dist" target.

I'll see if I can make a patch or two in the next few days.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-07-26  3:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:12 DTC 1.0.0 Release Coming? Jon Loeliger
2007-07-26  3:05 ` David Gibson [this message]
2007-07-26  7:25   ` David Gibson
2007-07-26 13:04   ` Jon Loeliger
2007-07-26 14:27     ` David Gibson
2007-07-26 15:21       ` Jon Loeliger
2007-07-27  1:33         ` David Gibson
2007-07-27  2:00           ` David Gibson
2007-07-31 21:11             ` Segher Boessenkool
2007-08-01  1:19               ` David Gibson
2007-08-06 19:33                 ` Segher Boessenkool
2007-08-06 13:48           ` Josh Boyer
2007-08-10  1:30             ` David Gibson
2007-08-10  1:37               ` Josh Boyer
2007-08-10  2:59                 ` David Gibson
2007-08-10 20:59                   ` Segher Boessenkool
2007-08-10 22:24                     ` Geoff Levand
2007-08-10 23:39                       ` Segher Boessenkool
2007-08-11  0:52                   ` Paul Mackerras
2007-08-11  1:35                     ` Geoff Levand
2007-08-12  9:26                       ` David Gibson
2007-08-13  1:39                         ` Stephen Rothwell
2007-08-12  9:25                     ` David Gibson
2007-08-10  2:13               ` Geoff Levand
2007-07-31 21:09 ` Segher Boessenkool
2007-08-01 23:35 ` Arnd Bergmann
2007-08-02  0:14   ` David Gibson

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=20070726030550.GA1149@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.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).