From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-tiny@selenic.com,
linux-kernel <linux-kernel@vger.kernel.org>,
celinux-dev@tree.celinuxforum.org
Subject: Re: 2.6.10-tiny1 released
Date: Sat, 8 Jan 2005 10:28:22 +0100 [thread overview]
Message-ID: <20050108092822.GA15875@kiste> (raw)
In-Reply-To: <20050108034522.GF2940@waste.org>
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
Hi,
Matt Mackall:
> This is a resync of the -tiny tree against 2.6.10.
> http://selenic.com/tiny/2.6.9-tiny1.patch.bz2
Umm, one of these version numbers is wrong.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-08 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 3:45 2.6.10-tiny1 released Matt Mackall
2005-01-08 9:28 ` Matthias Urlichs [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=20050108092822.GA15875@kiste \
--to=smurf@smurf.noris.de \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tiny@selenic.com \
--cc=mpm@selenic.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).