Commit docbook2man?

Started by Peter Eisentrautover 24 years ago4 messagesdocs
Jump to latest
#1Peter Eisentraut
peter_e@gmx.net

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?

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

#2Bruce Momjian
bruce@momjian.us
In reply to: Peter Eisentraut (#1)
Re: Commit docbook2man?

Seems we could put in /src/tools.

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?

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: Commit docbook2man?

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

#4Thomas Lockhart
lockhart@fourpalms.org
In reply to: Peter Eisentraut (#1)
Re: Commit docbook2man?

...

How big is docbook2man?

It is *very* small by our standards ;)

I agree that it should go into CVS so we don't lose the ability to
generate man pages.

- Thomas