linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: DTC 1.0.0 Release
Date: Fri, 10 Aug 2007 13:25:20 +1000	[thread overview]
Message-ID: <1186716320.13427.0.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070810012541.GE17370@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

On Fri, 2007-08-10 at 11:25 +1000, David Gibson wrote:
> On Thu, Aug 09, 2007 at 08:01:33PM -0500, Jon Loeliger wrote:
> > Hey guys,
> > 
> > Well, I tagged and released an official DTC v1.0.0 Release
> > and pushed it out to jdl.com just now.  You can grab the
> > git repo directly:
> > 
> >     git://www.jdl.com/software/dtc.git
> > 
> > or download a tarball here:
> > 
> >     http://www.jdl.com/software/dtc-1.0.0.tgz
> > 
> > As usual, please let me know of any issues with it.
> 
> Well, I'm not thrilled about the versioning, nor some inaccuracies in
> the new documentation.  But as you say in the commit message, it's
> about bloody time, we can fix the problems later.

Everyone knows not to use x.0.0 releases anyway, so hurry up and push
out 1.0.1 ;)

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-08-10  3:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  1:01 DTC 1.0.0 Release Jon Loeliger
2007-08-10  1:25 ` David Gibson
2007-08-10  3:25   ` Michael Ellerman [this message]
2007-08-10 21:21 ` Olaf Hering
2007-08-13  0:50   ` David Gibson
2007-08-13 18:30     ` Jon Loeliger

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=1186716320.13427.0.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=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).