linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: John Cherry <cherry@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.68
Date: Mon, 21 Apr 2003 19:12:40 +0100	[thread overview]
Message-ID: <20030421191240.A9681@infradead.org> (raw)
In-Reply-To: <1050948298.2293.70.camel@cherrypit.pdx.osdl.net>; from cherry@osdl.org on Mon, Apr 21, 2003 at 11:04:58AM -0700

>    Nightly linux-2.5 bk build:
>        www.osdl.org/archive/cherry/stability/linus-tree/running.txt
>    2.5 porting items:
>        www.osdl.org/archive/cherry/stability/linus-tree/port_items.txt
>    2.5 porting items history:
>        www.osdl.org/archive/cherry/stability/linus-tree/port_history.txt

404


  reply	other threads:[~2003-04-21 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 18:04 Linux 2.5.68 John Cherry
2003-04-21 18:12 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-20  3:11 Linus Torvalds
2003-04-20  4:57 ` Ben Collins

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=20030421191240.A9681@infradead.org \
    --to=hch@infradead.org \
    --cc=cherry@osdl.org \
    --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).