From: Andrew Morton <akpm@osdl.org>
To: Coywolf Qi Hunt <qiyong@fc-cn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why no -mm git tree?
Date: Tue, 10 Jan 2006 22:44:51 -0800 [thread overview]
Message-ID: <20060110224451.44c9d3da.akpm@osdl.org> (raw)
In-Reply-To: <20060111055616.GA5976@localhost.localdomain>
Coywolf Qi Hunt <qiyong@fc-cn.com> wrote:
>
> Why don't use a -mm git tree?
>
Because everthing would take me 100x longer?
I'm looking into generating a pullable git tree for each -mm. Just as a
convenience for people who can't type "ftp".
That'll just be a dump of the whole -mm lineup into git. I don't know how
workable it'll be - we'll see.
next prev parent reply other threads:[~2006-01-11 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 5:56 why no -mm git tree? Coywolf Qi Hunt
2006-01-11 6:38 ` Jeff Garzik
2006-01-11 6:44 ` Andrew Morton [this message]
2006-01-11 7:00 ` Coywolf Qi Hunt
2006-01-11 7:18 ` Andrew Morton
2006-01-11 12:36 ` Paolo Ciarrocchi
2006-01-11 17:11 ` Andrew Morton
2006-01-12 16:23 ` J. Bruce Fields
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=20060110224451.44c9d3da.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiyong@fc-cn.com \
/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).