From: Christoph Hellwig <hch@infradead.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [BK updates] fbdev changes updates.
Date: Tue, 29 Oct 2002 20:55:29 +0000 [thread overview]
Message-ID: <20021029205529.A2145@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0210291245410.14451-100000@maxwell.earthlink.net>; from jsimmons@infradead.org on Tue, Oct 29, 2002 at 12:46:16PM -0800
On Tue, Oct 29, 2002 at 12:46:16PM -0800, James Simmons wrote:
>
> OOps. Forgot the link.
>
> bk://fbdev.bkbits.net/fbdev-2.5
Does it still contain the random file movearounds?
next prev parent reply other threads:[~2002-10-29 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 20:45 [BK updates] fbdev changes updates James Simmons
2002-10-29 20:08 ` Dave Jones
2002-10-29 22:07 ` James Simmons
2002-10-29 22:31 ` Alan Cox
2002-10-29 22:38 ` James Simmons
2002-10-30 5:32 ` Antonino Daplas
2002-10-29 20:46 ` James Simmons
2002-10-29 20:55 ` Christoph Hellwig [this message]
2002-10-29 22:08 ` James Simmons
2002-10-29 21:18 ` Christoph Hellwig
2002-10-29 22:23 ` James Simmons
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=20021029205529.A2145@infradead.org \
--to=hch@infradead.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).