From: Jes Sorensen <jes@trained-monkey.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK FBDEV updates]
Date: 06 Jan 2003 20:26:44 -0500 [thread overview]
Message-ID: <m3heclagx7.fsf@trained-monkey.org> (raw)
In-Reply-To: James Simmons's message of "Mon, 6 Jan 2003 17:55:26 -0800 (PST)"
>>>>> "James" == James Simmons <jsimmons@infradead.org> writes:
James> Linus, please do a
James> bk pull http://fbdev.bkbits.net:8080/fbdev-2.5
James> This will update the following files:
James,
You seem to have forgotten to include the unified diff in your posting
posting to the list. Would you mind putting it somewhere.
Thanks,
Jes
next prev parent reply other threads:[~2003-01-07 1:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 1:55 [BK FBDEV updates] James Simmons
2003-01-07 1:26 ` Jes Sorensen [this message]
2003-01-07 5:19 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 0:24 [BK fbdev updates] James Simmons
2003-01-12 15:07 ` Jens Axboe
2003-01-13 0:15 ` Marcelo Pacheco
2003-01-15 22:02 ` James Simmons
2003-01-16 0:31 ` Marcelo Pacheco
2003-01-15 0:30 ` James Simmons
2003-01-08 19:19 [BK FBDEV updates] James Simmons
2003-01-01 1:17 [BK fbdev updates] James Simmons
2003-01-01 0:31 ` Dimitrie O. Paun
2003-01-01 1:47 ` Linus Torvalds
2003-01-01 2:22 ` James Simmons
2003-01-01 2:25 ` Linus Torvalds
2003-01-01 2:39 ` James Simmons
2003-01-02 6:59 ` David S. Miller
2002-11-09 2:46 Bom Luzares-Daplas
2002-11-02 4:06 [Linux-fbdev-devel] " Antonino Daplas
2002-11-08 0:01 ` James Simmons
2002-10-31 21:03 James Simmons
2002-10-30 21:42 James Simmons
2002-10-30 22:12 ` Russell King
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=m3heclagx7.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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).