Re: How to change -ko bit to -kb?

[Larry Jones]

Uwe Fritsch writes:
 
 I found some files in our repository which have a -ko bit set, but I
 would rather like to have them set to -kb. I tried to run "cvs admin
 -kb" on these files, but this does not change the bit.

That should have changed the default options in the repository file, it
just doesn't change the sticky options on the working files -- you need
to do a ``cvs up -kb'' on the same files to update the working directory
or delete the working directory and check it out again.

-Larry Jones

We seem to be out of gun powder. -- Calvin

.trunk patch refinement

[Stephen Cameron]

Ok, here's a refinement of my ".trunk' patch that gives
the trunk a branch-tag name, just like other branches
(from the user's perspective, the implementation is rather
different.)

You can also find this here:
http://www.geocities.com/dotslashstar/branch_patch.html

From HACKING:

* Writing patches (strategy)

[...] For features, the desirable attributes are that
the need is clear and that they fit nicely into the architecture of
CVS.  Is it worth the cost (in terms of complexity or any other
tradeoffs involved)?  Are there better solutions?

I'm not sure I know the answers to the above..., but you can have a
look at my code and ponder it.

If the design is not yet clear (which is true of most features), then
the design is likely to benefit from more work and community input.

Yes please, input could be nice.

Make a list of issues, or write documentation including rationales for
how one would use the feature.



Discuss it with coworkers, a
newsgroup, or a mailing list, and see what other people think.

This has been discussed several times in the past...with no real outcome. 

Distribute some experimental patches and see what people think.  The
intention is arrive at some kind of rough community consensus before
changing the "official" CVS.  Features like zlib, encryption, and
the RCS library have benefitted from this process in the past.

So far: ...silence... (the sound of crickets chirping maybe)

If longstanding CVS behavior, that people may be relying on, is
clearly deficient, it can be changed, but only slowly and carefully.
For example, the global -q option was introduced in CVS 1.3 but the
command -q options, which the global -q replaced, were not removed
until CVS 1.6.

I have carefully refrained from disturbing the longstanding (but
disturbing) behavior of the "HEAD" pseudo tag.

* Writing patches (tactics)

When you first distribute a patch it may be suitable to just put forth
a rough patch, or even just an idea.  But before the end of the
process the following should exist:

Check!

  - ChangeLog entry (see the GNU coding standards for details).

Check!

  - Changes to the NEWS file and cvs.texinfo, if the change is a
user-visible change worth mentioning.

Check!
  - Somewhere, a description of what the patch fixes (often in
comments in the code, or maybe the ChangeLog or documentation).

Check!
  - Most of the time, a test case (see TESTS).  It can be quite
frustrating to fix a bug only to see it reappear later, and adding
the case to the testsuite, where feasible, solves this and other
problems.
Check!

Include words like "I grant permission to distribute this patch under
the terms of the GNU Public License" with your patch.  By sending a
patch to [EMAIL PROTECTED], you implicitly grant this permission.

Check!

"I hereby grant permission to distribute this patch under
the terms of the GNU Public License"  -- Steve Cameron

So, of course my expectations are not that this will be checked
in, but maybe someone will point me to what I need to fix to move
things in that direction, or tell me not to bother.


Thanks,

-- steve

The patch is attached. Or you can get it here too:
http://www.geocities.com/dotslashstar/branch_patch.html




__
Do You Yahoo!?
Send instant messages with Yahoo! Messenger.
http://im.yahoo.com/


Index: NEWS
===
RCS file: /home2/cvsroot/ccvs/NEWS,v
retrieving revision 1.79
diff -c -r1.79 NEWS
*** NEWS2000/05/05 14:48:37 1.79
--- NEWS2000/06/18 04:19:30
***
*** 1,5 
--- 1,8 
  Changes since 1.10:
  
+ * New ".trunk" pseudo-branch-tag added which acts just like a branch
+   tag, but means the trunk.
+ 
  * The "cvs history" command output format has changed -- the date
  now includes the year and is given is ISO 8601 format (-mm-dd).
  
Index: doc/ChangeLog
===
RCS file: /home2/cvsroot/ccvs/doc/ChangeLog,v
retrieving revision 1.622
diff -c -r1.622 ChangeLog
*** ChangeLog   2000/06/14 17:41:56 1.622
--- ChangeLog   2000/06/18 04:19:47
***
*** 1,3 
--- 1,7 
+ 2000-06-18  Stephen Cameron [EMAIL PROTECTED]
+ 
+   * cvs.texinfo:  Document new ".trunk" pseudo branch tag.
+ 
  2000-04-03  Pavel Roskin  [EMAIL PROTECTED]
  
* cvs.texinfo (Telling CVS to notify you): Remove backslashes
Index: doc/cvs.texinfo
===
RCS file: /home2/cvsroot/ccvs/doc/cvs.texinfo,v
retrieving revision 1.489
diff -c -r1.489 cvs.texinfo
*** cvs.texinfo 2000/06/14 17:41:56