From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, "Buttchereit,
Axel (XL)" <XL@XLsigned.net>
Subject: Re: patch-scripts, CVS, bitkeeper and kernel-sources
Date: Tue, 1 Feb 2005 23:03:29 +0800 [thread overview]
Message-ID: <200502012303.37857.adaplas@hotpop.com> (raw)
In-Reply-To: <41FEC03B.1070401@XLsigned.net>
On Tuesday 01 February 2005 07:33, Buttchereit, Axel (XL) wrote:
> Hi,
>
> after reading "docco.txt" of "patch-scripts", browsing the mailing list
> archive and inspecting the "linux-fbdev" CVS repository on soureforge I'm a
> little confused.
>
> Where are the sources or rather how can I access the HEAD revision (of
> trunk, tags and/or branches) that are required when generating a patch?
>
> My intelfb-patch is based on 2.6.10 kernel sources that might have been
> patched already by gentoo (gentoo 2.6.10-r6), though I'm quite sure that
> "intelfb" was'nt touched. But 2.6.11-rc2-mm2 on kernel.org does obviously
> contain patches for "intelfb" that I wasn't aware of. (Maybe the patches
> that were recently posted here)
>
> Does that mean that I have to check "kernel.org" for latest patches (change
> sets)? What for is this (almost empty) "linux-fbdev" CVS repository? My
> first thought was that this is the place where current fbdev development is
> taken place and that "stable releases" are transmitted to "kernel.org".
>
> Right now I'm assuming that the truth is: I have to maintain a
> kernel-source-tree by my own and use the (quoting) "fragile" patch-scripts
> to apply bitkeeper diffs from kernel.org?
>
> Is this all because of linux using bitkeeper and not cvs, gnu/arch (tla) or
> subversion?
>
> Thanks for answering my stupid questions
You can consider Andrew's mm tree as the development tree. (I will push next
patch series soon, including yours). Note that in the -rc2 stage, only
bug-fixes will be pushed to mainline. Driver addition/enhancements will be
pushed to mainline in the next round, after 2.6.12 is released.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-02-01 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 23:33 patch-scripts, CVS, bitkeeper and kernel-sources Buttchereit, Axel (XL)
2005-02-01 15:03 ` Antonino A. Daplas [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=200502012303.37857.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=XL@XLsigned.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.