Re: cvs.texinfo updates? add/remove/tag

[Kevin R. Bulgrien]

> Yes. Do note that the cvs.1 man page is also
> extracted from the cvs.texinfo file.

It was actually the cvs.1 man page that I wanted
to fix since it is the resource I use the most.

> In the worst case, just provide the text and it
> can be turned into texinfo compatible format.

The format of the file is pretty simple.  I have
already written up one section and successfully
done a make cvs.1

> I use Emacs as my text editor and it does have a
> Texinfo mode which can help a little, but really
> any editor would do as well.

Uh oh, maybe I shouldn't mention that I use vim...

> You would want to provide unified diffs of the
> cvs.texinfo file with your changes.
>
> Please note that the cvs documentation is under
> the GNU Copyleft, so by sending in the diffs you
> should be willing to agree to let them be freely
> redistributed by anyone.

Yes.  This was my intention.

> I do see one possible problem. Your employer may
> have rights to the intellectual property you are
> suggesting be added. Especially considering the
> CONFIDENTIAL/PROPRIETARY banner that they seem to
> stick on the end of your e-mail.
>
> Unless you can get them to agree to release your
> proposed changes, you should probably just avoid
> writing anything at all as we would not be able to
> put them into the documentation if they arrive
> with the same disclaimer as you provided in this
> message.
> 
>      -- Mark

Yes, that footer is quite annoying.  Oddly, it used to only
get stuck on incoming mail, which was really bizarre
since it was appended to other people's mail...  I see
that is "fixed" now.  (Refreshing to note you assumed it
was beyond my control.)

The licensing will not be a problem.  While I did identify
the issue while working with CVS at work,  I am doing this
documentation effort at home on my own time, and I do
intend to submit it as my own work which is independent
of my employer.  To keep that more clear, I'll refrain from
using my employer's e-mail account for any further
activity on this thread.

Kevin R. Bulgrien
http://kbulgrien.home.att.net/