From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: powerpc.git tree
Date: Wed, 11 Jan 2006 10:24:57 -0500 [thread overview]
Message-ID: <76faf56ea70a1f2fe254367cda836c5f@embeddededge.com> (raw)
In-Reply-To: <17348.60119.801379.127209@cargo.ozlabs.ibm.com>
On Jan 11, 2006, at 6:24 AM, Paul Mackerras wrote:
> If that would cause people serious heartburn, I can instead abandon
> the powerpc.git tree and start a new development tree
> (powerpc-devel.git perhaps).
From past experience, creating another tree, especially something
called "devel" only caused more problems :-) Please, just do what
you think is best for the powerpc.git tree and we'll just move forward.
Thanks.
-- Dan
next prev parent reply other threads:[~2006-01-11 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 11:24 powerpc.git tree Paul Mackerras
2006-01-11 15:24 ` Dan Malek [this message]
2006-01-11 15:26 ` Jon Loeliger
2006-01-11 19:11 ` will schmidt
2006-01-15 5:53 ` Stephen Rothwell
2006-01-15 6:07 ` Paul Mackerras
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=76faf56ea70a1f2fe254367cda836c5f@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.