Re: cvs error: received broken pipe signal

in this section of the manual: https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC175 -- -------- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 505-844-7666 ___ Info-cvs mailing list Info-c

Re: Sourge Forge Repository Structure

ve to manage a system like that. ;) ) The only issues are those that always come with a large UNIX/LINUX system; managing user accounts, storage, and backups, and these are all people and resources issues, not technical issues. Regards Jain Pars -Original Message- From: Mark E. Ham

Re: Removing Without Committing

_ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 505-844-7666 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Sourge Forge Repository Structure

methodology is up to each project admin(s). However, if they're using CVS correctly the stable and development revisions should reside in the same repository, with the Stable revision(s) tagged and branched. -- Mark E. Hamilton Orion International Technologies, Inc. S

Re: Undo a Remove

at cvs add: use 'cvs commit' to add this file permanently % cat test7.dat Test Message. Test Message. -- -------- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 505-844-7666 ___ Info-cvs mailing l

Re: How to manage administrative file (quite long...)

or changelog to see if it worth the upgrading due to some new feature, thanks. If you don't want to upgrade to the 1.12.x feature verson of CVS you should still upgrade to the most recent stable version. There a number of bug fixes that have been made since 1.11.1p1. -- ---- Mark E

Re: How to get started

Rondal, Mark E. Hamilton wrote: Rondal, 5. Now you can start the remove/test cycle that Todd suggests, with the assistance of a Senior Developer. BTW, don't lose the test script/program that you use to validate that the production area is still working. In fact, you should commit it to

Re: How to get started

at makes all absoulte references into references relative to the root of the product hierarchy. This is a much better way to do it, but adding it after the fact can be tough. -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 505-844-7666 _

Re: CVS Annotate or FORCING users to comment their checkins

is through the Admin level? You can use the verifymsg administrative file to validate the log message prior to commits. <https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC172> -- -------- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laborat

Re: Clearing the stick option???

[EMAIL PROTECTED] wrote: So the sequence is then... > cvs admin -kkv Makefile > cvs up -A -r b_branch Makefile Correct? Yes. -- ---- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 84

Re: Clearing the stick option???

will clear the sticky tag. However, you can do cvs update -A -r b_branch Makefile -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 ___ Info-cvs mailing list Info-cvs@gnu.org http

Re: Clearing the stick option???

[EMAIL PROTECTED] wrote: I have a text file that, for some reason, has a -kb sticky option. How do I clear it via cvs admin? cvs admin -kkv file.txt cvs update -A file.txt -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666

Re: tagging an alias module

Doh! I left out a really important '!'. Sorry. Your module should be: mymodule -a !Project/Web/Clientx Project/Web (See section C.1.4 of Cederqvist for a little more info. ;) Mark E. Hamilton wrote: Jean-Pierre, Jean-Pierre Sevigny wrote: Hi, I have a module, say "mymodule"

Re: tagging an alias module

rtag test_tag1 mod_test1 cvs rtag: Tagging test1 cvs rtag: Ignoring test1/test2 sahp6613% cvs rtag test_tag2 mod_test2 cvs rtag: Tagging test1 cvs rtag: Tagging test1/test2 cvs rtag: Tagging test1/test2/rtest cvs rtag: Tagging test1/test2/rtest/null cvs rtag: Tagging test1/test2/rtest/null/a -

Re: Odd typo in update message?

ce that's never going to happen, I'd suggest that you consider whether this convention is really doing what you want it to do, and is worth adhering to. Mark E. Hamilton wrote: Is this in fact a typo, or is there some other meaning/use for this `name' pattern? -- --

Odd typo in update message?

ere some other meaning/use for this `name' pattern? -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Checkout after a change

('^' is a csh substitution operator, and I try to avoid csh), but when I type ^test in bash I get the same error -bash: :s^test: substitution failed -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 __

Re: Info-cvs Digest, Vol 27, Issue 40

Spiro Trikaliotis wrote: If you are working from Unix boxes solely, this works as expected. If not, chances are you have to check in a new binary file. You mean that there are other computers besides Unix-like systems? ;) Thanks. -- Mark E. Hamilton Orion International

Re: Info-cvs Digest, Vol 27, Issue 40

okay; just the working version is corrupted. The instructions I've given our users is to do this: cvs admin -kb cvs update which has always seemed to work in the past. Are there situations where the repository file could be corrupted, so that this wouldn't work? -- -

Re: keywords for branches and tags

s didn't think it needed to fetch the file again. -- ---- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Can I turn off merge conflict markers?

Mark E. Hamilton wrote: A fourth approach would be to do the 'cvs update' to merge everything that can be merged successfully, and then use something like this to automatically select one of the two choices in the conflict lines: #!/bin/bash for file in $(cvs -q update | egrep '^

Re: Can I turn off merge conflict markers?

Todd Denniston wrote: "Mark E. Hamilton" wrote: [EMAIL PROTECTED] wrote: When you get a file where automatic merge fails CVS will report a merge conflict and then modify the offending file with conflict markers: <<<<<<<< >>>>>>

Re: Can I turn off merge conflict markers?

r that will retain any changes that were successfully merged. The caveat of course is that you need to run your tests after the update, because even changes that successfully merged might still be logically incorrect with the changes made in the sandbox. -- -

Re: Change a keyword for another keyword

history[^\$]*/$Log/g' $f > blarg && mv blarg $f done -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Change a keyword for another keyword

(--in-place)' option. (I've used sed for years, and didn't know about it until just now. Gotta read those man pages more frequently. ;) ) -- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 844-7666 ___

Re: rtag assertion in recurse.c:642

All, I must apologize if I wasted anyone's time. A little more reasearch showed me that this is going to be fixed in 1.11.18. In fact, I submitted a bug report on this nearly a year ago, but I'd forgotten. Sorry. -- -------- Mark E. Hamilton Orion International Technologies, I

rtag assertion in recurse.c:642

x27;\0' ? (char *) (size_t) (repository) : (((const char *) ("/./"))[1] == '\0' ? (__extension__ (__builtin_constant_p (((const char *) ("/./"))[0]) && (((const char *) ("/./"))[0]) == '\0' ? (char *) __rawmemchr (repository, ((const char *) (