From: Jon Loeliger <jdl@freescale.com>
To: David Gibson <david@gibson.dropbear.id.au>
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: Thu, 01 Nov 2007 09:04:42 -0500 [thread overview]
Message-ID: <1193925881.15380.8.camel@ld0161-tx32> (raw)
In-Reply-To: <20071031225624.GB16119@localhost.localdomain>
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.
The Linux Community happily embraced and used early
versions of git, installing it themselves if needed,
long before it was available in _any_ distro.
Thanks,
jdl
next prev parent reply other threads:[~2007-11-01 14:08 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 [this message]
2007-11-02 0:34 ` 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=1193925881.15380.8.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=gerald.vanbaren@ge.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