From: Dirk Vleugels vleugels@do.isst.fhg.de
Subject: format for source diffs
Date: Sun, 20 Aug 1995 15:10:54 -0400 [thread overview]
Message-ID: <19950820191054.U9OcaC50JzJtSLbJKNoeSZLqwnIMw474WRLd3A8x2aU@z> (raw)
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
next reply other threads:[~1995-08-20 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-20 19:10 Dirk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-21 21:28 Brian
1995-08-21 12:20 Dirk
1995-08-21 5:04 Vadim
1995-08-21 3:26 jmk
1995-08-21 3:25 jmk
1995-08-20 14:24 Scott
1995-08-20 4:09 jmk
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=19950820191054.U9OcaC50JzJtSLbJKNoeSZLqwnIMw474WRLd3A8x2aU@z \
--to=9fans@9fans.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).