From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@freescale.com>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>,
Jerry Van Baren <gerald.vanbaren@ge.com>
Subject: Re: libfdt as its own repo and submodule of dtc?
Date: Fri, 2 Nov 2007 11:34:06 +1100 [thread overview]
Message-ID: <20071102003406.GA19839@localhost.localdomain> (raw)
In-Reply-To: <1193925881.15380.8.camel@ld0161-tx32>
On Thu, Nov 01, 2007 at 09:04:42AM -0500, Jon Loeliger wrote:
> On Wed, 2007-10-31 at 17:56, David Gibson wrote:
>
> > I'm not too keen on using a git feature that's more recent than the
> > git in most distros.
>
> I'm going to consider this argument null and void on two fronts:
>
> You don't use git for patch generation and submission anyway.
True. It wasn't clear to me whether using this git-submodule thing
would also affect pulling.
> The Linux Community happily embraced and used early
> versions of git, installing it themselves if needed,
> long before it was available in _any_ distro.
I don't think this is a comparable situation. For one, dtc does not
have the clout of Linux. For another, at the time there was hardly
anything in the way of suitable solutions that were out there in
distros. That's not the case now - we can do nearly everything we
want with the git in recent distros, I don't think there's call to
require a newer version for one extra feature.
--
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
prev parent reply other threads:[~2007-11-02 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 15:23 libfdt as its own repo and submodule of dtc? Kumar Gala
2007-10-30 15:56 ` Jon Loeliger
2007-10-30 17:14 ` Jerry Van Baren
2007-10-30 23:40 ` David Gibson
2007-10-31 12:50 ` Jerry Van Baren
2007-11-01 6:55 ` Kumar Gala
2007-10-31 22:56 ` David Gibson
2007-11-01 14:04 ` Jon Loeliger
2007-11-02 0:34 ` David Gibson [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=20071102003406.GA19839@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=gerald.vanbaren@ge.com \
--cc=jdl@freescale.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).