bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Mark D. Baushke
Subject: Re: cvs.texinfo updates? add/remove/tag
Date: Sat, 12 Aug 2006 00:06:56 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bulgrien, Kevin <address@hidden> writes:

> Are the CVS developers amenable to accepting
> patches against cvs.texinfo to add sections for
> the add, remove, and tag commands?

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

> I realize these sections might be simplistic,
> but in particular, the add/remove sections would
> be a good place to record the fact that a cvs
> add is the appropriate way to undo a cvs remove
> when the removed file has not yet been
> committed.

Okay.

> I have only infrequently messed with man page
> sources and that was years ago. I don't know
> anything about texinfo, so it would be a
> stretch, but I could attempt to tackle this by
> simply following the example of other sections
> that are similar. I don't want to attempt this
> if there would be a strong chance such a patch
> would be rejected outright, though naturally I
> would expect it to be subject to review.

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

> If I were to do this, is it normal to simply
> edit the texinfo file with a plain-text editor,
> or is that the masochistic way to do it?

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.

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.

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

> --- 
> Kevin R. Bulgrien
> Design and Development Engineer
> General Dynamics C4 Systems
> http://www.gdsatcom.com/
> VertexRSI
> 
> 
> CONFIDENTIAL/PROPRIETARY 
> 
> Unless otherwise indicated, all information (including attachments)
> contained in this e-mail communication is confidential and proprietary
> information exclusively owned by the sender and/or its related or affiliated
> companies and shall not, without the prior written consent of the sender, be
> used, disclosed, distributed or reproduced, in whole or in part, by anyone
> other than the individual or entity to whom this communication is addressed
> exclusively for the purpose expressly indicated in this communication.
> 
> This e-mail communication is intended for the use of the individual or
> entity to whom it is addressed.  If you are not the intended recipient of
> this communication, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.  If
> you have received this communication in error, please destroy any copies,
> electronic, paper or otherwise that you may have.
> 
> 
> _______________________________________________
> Bug-cvs mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/bug-cvs
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFE3X4QCg7APGsDnFERAoUBAJ0WMnpEvRbIZEzg/JvXw+NGLiCEHgCg4kwk
KlWTpRgZRN/VgN0a3cXqHAU=
=l6UH
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]