From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0-test1-ac1
Date: Mon, 14 Jul 2003 22:50:45 +0200 [thread overview]
Message-ID: <20030714205045.GB27456@louise.pinerecords.com> (raw)
In-Reply-To: <200307142016.h6EKGDe02631@devserv.devel.redhat.com>
> [alan@redhat.com]
>
> 2.6.0-test1-ac1
Alan, are you planning to merge in the mergeable bits of your
original 2.5-ac or is this to be a different-purpose-branch(tm)?
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-14 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 20:16 Linux 2.6.0-test1-ac1 Alan Cox
2003-07-14 20:50 ` Tomas Szepe [this message]
2003-07-14 20:51 ` Joshua Kwan
2003-07-15 21:16 ` 2.6.0-test1-ac1: cs4281m.c doesn't compile Adrian Bunk
2003-07-15 23:53 ` Alan Cox
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=20030714205045.GB27456@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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).