Date: Thu, 18 Nov 1999 21:33:15 +0100 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Nik Clayton <nik@freebsd.org> Cc: Alexey Zelkin <phantom@cris.net>, doc@freebsd.org Subject: Re: tutorials Message-ID: <19991118213315.D35248@daemon.ninth-circle.org> In-Reply-To: <19991118081917.D93488@kilt.nothing-going-on.org> References: <19991115173853.A6833@scorpion.crimea.ua> <19991115201733.B19819@daemon.ninth-circle.org> <19991116080341.A92155@kilt.nothing-going-on.org> <19991116204509.A99933@daemon.ninth-circle.org> <19991117204338.B17330@scorpion.crimea.ua> <19991117203140.C18826@daemon.ninth-circle.org> <19991118081917.D93488@kilt.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-On [19991118 21:25], Nik Clayton (nik@freebsd.org) wrote: >On Wed, Nov 17, 1999 at 08:31:40PM +0100, Jeroen Ruigrok/Asmodai wrote: >> >> So be my guest. It wouldn't hinder me. I think I am going to import >> >> the 2.x DDWG into my document as 2.x reference. Anyone know how to do a >> >> repo-cpoy? =) >> > >> >Why do you need repo-copy ? You wanna save history of development ? >> >> For myself. That and I want to know how it is done. > >Ah, I see. So if you're new document was going to be > > .../articles/writing-device-drivers/article.sgml > >(for example) then you want the existing tutorials/ddwg/ddwg.sgml copied >in to place first. Yeah. Locally. =) >OK, we could do it. But if you're document is going to be a complete >rewrite then with your first commit you will be deleting all the old lines >and adding in new ones. This isn't particularly useful from a CVS >historian point of view, because the diff will be huge. It will be a rewrite. So many things need to be covered. >Keep in mind that anyone that's in a position to see the history for your >new document should be in a position to see the history for the old document >as well. You might want to include a URL to the CVSWeb interface for the >old document in yours. Sound like a good alternative. >> As I said above. Be my guest. The new DDWG will be 2.x, 3.x and 4.x as >> still a lot of people seem to want to support 2.x and I hope to provide >> migrating tips. > >That's good news. Perhaps we could use this article to prototype the new >mechanism for including OS version specific information in the documentation? Let me know what you came up with to use this. I would be happy to test it, since I am going to do more and more DocBook related things at work. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; Network/Security Specialist BSD: Technical excellence at its best Who looks under the surface does so at his own risk... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991118213315.D35248>