From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: DTC 1.0.0 Release Coming?
Date: Thu, 9 Aug 2007 20:37:54 -0500 [thread overview]
Message-ID: <20070809203754.2e9192c5@zod.rchland.ibm.com> (raw)
In-Reply-To: <20070810013001.GF17370@localhost.localdomain>
On Fri, 10 Aug 2007 11:30:01 +1000
David Gibson <dwg@au1.ibm.com> wrote:
> > Except didn't you say you were going to work with Stephen to get DTC
> > into the kernel source itself? Keeping things similar to Kbuild might
> > help in that effort.
>
> Actually, after discussions with Stephen and Paulus, we decided not to
> take this route. In any case having Kbuild like versioning wouldn't
> actually help us any in integrating into a full Kbuild system.
Can you elaborate why you decided not to? I'm just curious.
> > > Have a look at the patch I posted. I haven't sufficiently tested it
> > > yet, but it should be able to generated version info for a tarball too
> > > (provided the .git-manifest file is included, and I'm intending that
> > > will be build by a make dist target). It will give both the
> > > git-derived based version, and a file content derived hash so we can
> > > robustly tell different builds apart, all with less code than the
> > > current system.
> >
> > That may be. But I don't see the current approach being too much of a
> > problem either. Especially given that it's already there and it
> > works. Oh, and you sent out your patch saying it wasn't ready for
> > merge and with no sign off. Small but important issues to fix I'd
> > think.
>
> Yeah, it lacks a make dist target, and needs a bit more work to
> support that properly. Never mind, I'll revisit this post the 1.0
> release.
Ok.
josh
next prev parent reply other threads:[~2007-08-10 1:38 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
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 [this message]
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=20070809203754.2e9192c5@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=dwg@au1.ibm.com \
--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).