From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: fbdev trees
Date: Tue, 18 May 2004 15:54:35 +1000 [thread overview]
Message-ID: <1084859674.15182.28.camel@gaston> (raw)
Hi James !
I'm trying to follow you tree but I'm lost. It seems you have both an
fbdev-2.5 and an fbdev-2.6 tree containing completely different code
bases. I used to sync a local tree with fbdev-2.5 but it stopped working
completely with one of your latest code drops of last week. Today I
noticed you had fbdev-2.6 too, but with what seem older version of some
stuffs (or am I confused ?)
So which is which ?
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next reply other threads:[~2004-05-18 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 5:54 Benjamin Herrenschmidt [this message]
2004-05-18 16:06 ` fbdev trees 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=1084859674.15182.28.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).