From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: Commit docbook2man?
Date: Mon, 03 Sep 2001 19:17:10 -0400
Message-ID: <11881.999559030@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0108301638020.679-100000@peter.localdomain>
References: <Pine.LNX.4.30.0108301638020.679-100000@peter.localdomain>
Peter Eisentraut <peter_e@gmx.net> writes:
> Since we're slowly nearing a release, I'm already starting to hack around
> the docbook2man stuff again. To produce acceptable results several
> patches are required against the upstream release, and I'd like to have
> those recorded somewhere, i.e., our CVS rep. That way we can get a few
> more people testing the man pages before release.
> Should I import the original first and then commit the patches afterwards,
> or should I import the patches as separate files, or is anyone keen about
> vendor branches?
How big is docbook2man? I'm unenthused about adding a large chunk of
code to our distribution that's just a copy of someone else's
distribution.
If it's only a few K of source then replicating it in our distro might
make sense ... else I'd vote for just putting the required patch diffs
into a README or some such file.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net
Subject: Re: Commit docbook2man?
In-Reply-To: <11881.999559030@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox