format for source diffs

format for source diffs

[Vadim]

From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>

>The bundle plus diff would work, but it might be nice to take advantage
>of patch's functionality, since most people will be using it anyway and
>it can automatically create new files from context diffs built with -Nc
>or -Nu.  That would require augmenting /bin/diff or porting gnu diff,
>of course.

Aw!  The next thing to port will be EMACS :)

An illustration to my point on functional completeness.

--vadim

format for source diffs

[Brian]

vadim writes:
|Aw!  The next thing to port will be EMACS :)

Isn't it already (unforunately) done? I saw the man page (recommended reading).

format for source diffs

[Dirk]

>>>>> "jmk" == jmk  <jmk@plan9.att.com> writes:

Hello,

    jmk> the 868 can be described in vgadb as a vision864. i don't
    jmk> know what the clock or ramdac is on that board.

Markus.Friedl@informatik.uni-erlangen.de
wrote:

The SPEA MirageP64 (2MB DRAM) has a:
- S3 86C716 SDAC RAMDAC and Clockchip (BIOS 4.xx)
- 20C498 or 21C498 RAMDAC, ICS2595 Clockchip (BIOS 3.xx)
(according to the X11R6/XFree3.1.2 documents)

Now, how to use this informations? Is it possible to get this card working 
with the current pcdist?

Thanx for any clue

Dirk

format for source diffs

[jmk]

	As far as i can see, i like the system. The 8c is fast, giving great
	turn around times with writing and debugging. I'm only able to use 640x480x1.
	(my card is a Spea Mirage S3 with 868 chip and 2MB dram). Anyone know if i
	can patch the vgadb to work with this chip?

the 868 can be described in vgadb as a vision864. i don't know what the clock
or ramdac is on that board.

format for source diffs

[jmk]

i can't say i'm thrilled about either of those options.

------ original message follows ------

>From cse.psu.edu!9fans-outgoing-owner Sun Aug 20 10:35:54 EDT 1995
Received: by colossus.cse.psu.edu id <45565>; Sun, 20 Aug 1995 10:25:06 -0400
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by colossus.cse.psu.edu with SMTP id <45561>; Sun, 20 Aug 1995 10:24:50 -0400
Received: from localhost by galapagos.cse.psu.edu with SMTP id <12684>; Sun, 20 Aug 1995 10:24:54 -0400
To:	9fans@cse.psu.edu
Subject: Re: format for source diffs 
In-reply-to: Your message of "Sun, 20 Aug 1995 00:09:29 EDT."
             <95Aug20.005926edt.46381@colossus.cse.psu.edu> 
Date:	Sun, 20 Aug 1995 10:24:41 -0400
From:	Scott Schwartz <schwartz@galapagos.cse.psu.edu>
Message-Id: <95Aug20.102454edt.12684@galapagos.cse.psu.edu>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu

jmk@plan9.att.com writes:
| I'd like to make the source changes for aux/vga available, what should the 
| format be?

The bundle plus diff would work, but it might be nice to take advantage
of patch's functionality, since most people will be using it anyway and
it can automatically create new files from context diffs built with -Nc
or -Nu.  That would require augmenting /bin/diff or porting gnu diff,
of course.

format for source diffs

[Dirk]

Hello,

>>>>> "jmk" == jmk  <jmk@plan9.att.com> writes:

    jmk> I'd like to make the source changes for aux/vga available,
    jmk> what should the format be? The changes include new files as
    jmk> well as diffs. I was thinking of a bundle containing the new
    jmk> files plus one file containing the output from diff
    jmk> /n/juke/plan_9/sys/src/cmd/aux/vga /sys/src/cmd/aux/vga
    jmk> (/n/juke/plan_9 contains the distribution cd).

The right place for a few questions. I installed the pcdist last night and
suceeded! I screwed my ide disk one time, but who cares for MS-* anyways
(i also have a backup ;)

As far as i can see, i like the system. The 8c is fast, giving great
turn around times with writing and debugging. I'm only able to use 640x480x1.
(my card is a Spea Mirage S3 with 868 chip and 2MB dram). Anyone know if i
can patch the vgadb to work with this chip?

In fact, my main question is: Does it make sense to put  work in the
attempt to work with the pcdist. It lacks the man pages, most binarys (as
far as i can see) and (of course) the source. Is it possible to enhance the
system by hand (get 386 binaries from the net &&| free sources?). I used
80MB for the installation with this thought in mind. Is the documentation
available on the net? (maybe parts of it?)

Thanx for any advice

Dirk

ps: ignore my lousy english spelling

format for source diffs

[Scott]

jmk@plan9.att.com writes:
| I'd like to make the source changes for aux/vga available, what should the 
| format be?

The bundle plus diff would work, but it might be nice to take advantage
of patch's functionality, since most people will be using it anyway and
it can automatically create new files from context diffs built with -Nc
or -Nu.  That would require augmenting /bin/diff or porting gnu diff,
of course.

format for source diffs

[jmk]

I'd like to make the source changes for aux/vga available, what should the 
format be? The changes include new files as well as diffs. I was thinking of
a bundle containing the new files plus one file containing the output from
	diff /n/juke/plan_9/sys/src/cmd/aux/vga /sys/src/cmd/aux/vga
(/n/juke/plan_9 contains the distribution cd).