All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Solares <solca@guug.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Merge of Luca and Ben's sysfs work for Radeon
Date: Fri, 26 Sep 2003 02:39:46 -0600	[thread overview]
Message-ID: <20030926083946.GA14350@guug.org> (raw)
In-Reply-To: <20030926025744.80379.qmail@web14905.mail.yahoo.com>

On Thu, Sep 25, 2003 at 07:57:44PM -0700, Jon Smirl wrote:
> The merged tree is a copy of everything in Linus' tree plus our fbdev work.
> Just treat it like a normal kernel tree.
> 
> make proper
> copy your config
> make oldconfig
> make
> 
> The tree contains all of:
> test5
> fbdev work
> hundreds of patches in the Linus tree past test5
> 
> To make sure it is absolutely up to date with Linus, cd into it and:
> bk pull bk://linux.bkbits.net/linux-2.5
> This will pull the up to the minute changes from Linus' own tree into yours.

done, it finish correctly with:

Consistency check passed, resolve complete.

> To see the diffs from test5 to present:
> bk revtool and find last revision number, probably something like 1.1303.
> bk export -tpatch -rv2.6.0-test2,1.1303 -h >../patch
> 
> There will be a lot of diffs, Linus is about ready to tag test6.
> 
> To look at a specific file:
> bk revtool file-name
> 
> Now that you have a bk tree you don't have to wait for a tagged release. Just
> pull the changes fron Linus' tree when you want to update.

Probably am doing something wrong because there are no
sane files, just s.*.{c,h} binaries in SCCS subdir so i
can't treat it normally:

solca@appsrv:~/devel/radeon$ ls drivers/video/aty/SCCS/
s.aty128fb.c    s.atyfb.h         s.mach64_ct.c      s.mach64_gx.c  s.radeon_base.c  s.radeon_i2c.c      s.radeon_pm.c
s.atyfb_base.c  s.mach64_accel.c  s.mach64_cursor.c  s.Makefile     s.radeonfb.h     s.radeon_monitor.c  s.xlinit.c

-solca



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-26  8:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25  6:05 Merge of Luca and Ben's sysfs work for Radeon Jon Smirl
2003-09-25 19:21 ` Otto Solares
2003-09-25 20:01   ` Kronos
2003-09-25 23:48     ` Otto Solares
2003-09-26  0:10       ` Jon Smirl
2003-09-26  2:36         ` Otto Solares
2003-09-26  2:57           ` Jon Smirl
2003-09-26  8:39             ` Otto Solares [this message]
     [not found]               ` <20030926171144.GA1380@dreamland.darkstar.lan>
2003-09-26 17:43                 ` Otto Solares
2003-09-26  3:03           ` Jon Smirl
2003-09-26 17:51             ` Otto Solares
2003-09-25 20:35   ` Jon Smirl
2003-09-25 23:49     ` Otto Solares
2003-09-26 18:23 ` radeonfb work (WAS: Merge of Luca and Ben's sysfs work for Radeon) Benjamin Herrenschmidt

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=20030926083946.GA14350@guug.org \
    --to=solca@guug.org \
    --cc=jonsmirl@yahoo.com \
    --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.