From: Jon Loeliger <jdl@jdl•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Re: [PATCH 0/2] Move DTC Technical specs out of b-w-o.txt into DTC Repo
Date: Thu, 12 Jul 2007 08:03:07 -0500 [thread overview]
Message-ID: <E1I8yK3-0003UC-Fk@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 12 Jul 2007 02:01:07 CDT." <BFA74155-D32C-41F5-B61C-D9CE89A29B9B@kernel.crashing.org>
So, like, the other day Kumar Gala mumbled:
>
> On Jul 11, 2007, at 4:45 PM, Jon Loeliger wrote:
>
> > Folks,
> >
> > Here are two patches, one to the kernel, the other to
> > the DTC repo, that moves the technical description
> > portions of the booting-without-of.txt documentation
> > out of the kernel and into the DTC repository.
>
> Why remove it from the kernel? It seems like this part should change
> infrequently and it would be good to keep its documentation with the
> kernel as well?
Well, all the usual reasons. It will be improving over time,
and it makes much more sense to keep the documntation about
a system within the repository for that system. And rather
than have two copies, one of which will get out of sync,
I feel it makes more sense to relocate the DTC technical
descriptions to the DTC repository where it belongs.
And speaking of which, I will also be removing the already extant
and already way out of data copy of the booting-without-of.txt
from the DTC repo as well.
If a small summary of say, DTC command line usage is left in
b-w-o.txt as a Quick Ref, I'm fine with that, of course.
Thanks,
jdl
prev parent reply other threads:[~2007-07-12 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 21:45 [PATCH 0/2] Move DTC Technical specs out of b-w-o.txt into DTC Repo Jon Loeliger
2007-07-12 7:01 ` Kumar Gala
2007-07-12 13:03 ` Jon Loeliger [this message]
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=E1I8yK3-0003UC-Fk@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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