Re: Viewing a list of projects
>--- Forwarded mail from [EMAIL PROTECTED] >Robert Thorpe writes: >> >> What you are saying is that I should make a pointless alias in the >> modules file to the modules in question and whenever I wish to >> create a new module I must do the same. >It's not pointless, it allows co -c to provide useful information. :-) >> I don't know how to >> write module file entires, I will have to learn and then add the >> pointless entries you describe. I could but why should I? >It is trivially easy -- all you need is something like: > foo foo > bar bar >The module file can be quite useful -- I'm not sure why you're so >opposed to actually learning about useful features of the software >you're using. Normally I would agree, but it turns out that the modules database happens to be one of the more broken features of CVS. The usefulness of it for anything other than just getting "cvs co -c" to work is definitely open to question, and the actual harm it can bring about is worth some discussion (particularly about possible repairs or replacement). >--- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Viewing a list of projects
On 4 Dec 2001, at 12:12, Jerry Nairn wrote: > There is something strange about your CVSROOT setting. It looks like you > have: > ":pserver:rthorpe@cvsserver:/export/ > cvsroot" > I would have thought that the line was just wrapped by your email program, > but that line is shorter than other lines which weren't broken. Sorry, I use Pegasus mail which sometimes looks like it breaks lines almost at random, it was originally one line before pasting. > This: "protocol error: is not absolute" > looks like a problem with CVSROOT, not an argument to "cvs co". An absolute > path is only required for the cvs repository. cvs co modulename works fine. The information in this e-mail is for use by the addressee(s) only. If you are not the intended recipient, please notify us immediately and delete the message from your computer. No liability or responsibility is accepted for viruses and it is your responsibility to scan attachments (if any). Opinions and views expressed in this email are those of the sender and do not reflect the opinions and views of antenova Ltd. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
Robert Thorpe writes: > > What you are saying is that I should make a pointless alias in the > modules file to the modules in question and whenever I wish to > create a new module I must do the same. It's not pointless, it allows co -c to provide useful information. :-) > I don't know how to > write module file entires, I will have to learn and then add the > pointless entries you describe. I could but why should I? It is trivially easy -- all you need is something like: foo foo bar bar The module file can be quite useful -- I'm not sure why you're so opposed to actually learning about useful features of the software you're using. > Is the attitude of the CVS developers "it was hard to write so it > should be hard to use?" No, the attitude of the (all volunteer) CVS developers is that we prefer to apply our (very limited) resources to more important problems. -Larry Jones No one can prove I did that!! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Viewing a list of projects
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 04, 2001 8:08 AM > Robert Thorpe writes: > > > > Is there any plans to introduce a command to do this more directly? > > There has been a patch posted here to add a "cvs ls" command. I have to agree that this is more of a problem than it should be, but here's a neat trick: cvs -nt co . Assuming top level repository directories named foo, bar, and baz, this will give you output like: cvs checkout: notice: main loop with CVSROOT=:pserver:name@server:/somecvsroot S-> do_module (., Updating, , ) S-> do_module (., Updating, , ) S-> unlink(./CVS/Entries.Static) cvs server: Updating . cvs server: New directory `CVSROOT' -- ignored cvs server: New directory `bar' -- ignored cvs server: New directory `baz' -- ignored cvs server: New directory `foo' -- ignored It only works this well on the top level, but that helps. Cheers, Jerry ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
On 4 Dec 2001, at 11:07, Larry Jones wrote: > Robert Thorpe writes: > > > > Is there any plans to introduce a command to do this more directly? > > There has been a patch posted here to add a "cvs ls" command. Adding it > is very low priority since you can always just add entries to the > modules file so that "cvs co -c" will work. What you are saying is that I should make a pointless alias in the modules file to the modules in question and whenever I wish to create a new module I must do the same. I don't know how to write module file entires, I will have to learn and then add the pointless entries you describe. I could but why should I? Surely the purpose of software is to provide an easy and powerful ways to do things. CVS ought to provide a command so that the modules can be listed. It wouldn't take a day to write and every user would appreciate it. Is the attitude of the CVS developers "it was hard to write so it should be hard to use?" The information in this e-mail is for use by the addressee(s) only. If you are not the intended recipient, please notify us immediately and delete the message from your computer. No liability or responsibility is accepted for viruses and it is your responsibility to scan attachments (if any). Opinions and views expressed in this email are those of the sender and do not reflect the opinions and views of antenova Ltd. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
Robert Thorpe writes: > > Is there any plans to introduce a command to do this more directly? There has been a patch posted here to add a "cvs ls" command. Adding it is very low priority since you can always just add entries to the modules file so that "cvs co -c" will work. -Larry Jones The living dead don't NEED to solve word problems. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
This doesn't work because they don't have entries in the module file. It seems to be a very simple thing to do that CVS makes very difficult, however: cvs history -a Gives me all the information I need to know. This is a list of the history of the modules in the the repository. In the future however it will inevitably become quite a long file. Is there any plans to introduce a command to do this more directly? On 3 Dec 2001, at 13:56, Larry Jones wrote: > Robert Thorpe writes: > > > > My company has a CVS server with several(5) projects on it, in > > order to access them I must be able to name them, I can't always > > remember the name, In particular I can't remember which words > > begin with capitals and which don't. Is there a way to list all the > > projects in the repository? > > If they have entries in the modules file, you can use "cvs co -c". > > -Larry Jones > > TIME?! I just finished the first problem! -- Calvin > The information in this e-mail is for use by the addressee(s) only. If you are not the intended recipient, please notify us immediately and delete the message from your computer. No liability or responsibility is accepted for viruses and it is your responsibility to scan attachments (if any). Opinions and views expressed in this email are those of the sender and do not reflect the opinions and views of antenova Ltd. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
This doesn't work because they don't have entries in the module file. It seems to be a very simple thing to do that CVS makes very difficult, however: cvs history -a Gives me all the information I need to know. This is a list of the history of the modules in the the repository. In the future however it will inevitably become quite a long file. Is there any plans to introduce a command to do this more directly? On 3 Dec 2001, at 13:56, Larry Jones wrote: > Robert Thorpe writes: > > > > My company has a CVS server with several(5) projects on it, in > > order to access them I must be able to name them, I can't always > > remember the name, In particular I can't remember which words > > begin with capitals and which don't. Is there a way to list all the > > projects in the repository? > > If they have entries in the modules file, you can use "cvs co -c". > > -Larry Jones > > TIME?! I just finished the first problem! -- Calvin > The information in this e-mail is for use by the addressee(s) only. If you are not the intended recipient, please notify us immediately and delete the message from your computer. No liability or responsibility is accepted for viruses and it is your responsibility to scan attachments (if any). Opinions and views expressed in this email are those of the sender and do not reflect the opinions and views of antenova Ltd. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Viewing a list of projects
Title: RE: Viewing a list of projects ... or istall TCL\TK in order to enable shell command and using macros get the list of available modules on the server. -Original Message- From: Marcus Crafter [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 11:24 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Viewing a list of projects Hi Robert, On Mon, Dec 03, 2001 at 06:27:29PM -, Robert Thorpe wrote: > My company has a CVS server with several(5) projects on it, in > order to access them I must be able to name them, I can't always > remember the name, In particular I can't remember which words > begin with capitals and which don't. Is there a way to list all the > projects in the repository? It might not be possible in your environment, but I'd recommend installing cvsweb or viewcvs. It will let you see what projects are in the repository amongst other things. Hope that helps. Cheers, Marcus -- . ,,$, Marcus Crafter ;$' ': Computer Systems Engineer $: : Managesoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$, _/\ &&:' 60327 Frankfurt Germany ' /( &&& \_&&&&' Email : [EMAIL PROTECTED] &&&&. Business Hours : +49 69 9757 200 &&&&&&&: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Viewing a list of projects
Hi Robert, On Mon, Dec 03, 2001 at 06:27:29PM -, Robert Thorpe wrote: > My company has a CVS server with several(5) projects on it, in > order to access them I must be able to name them, I can't always > remember the name, In particular I can't remember which words > begin with capitals and which don't. Is there a way to list all the > projects in the repository? It might not be possible in your environment, but I'd recommend installing cvsweb or viewcvs. It will let you see what projects are in the repository amongst other things. Hope that helps. Cheers, Marcus -- . ,,$, Marcus Crafter ;$' ':Computer Systems Engineer $: : Managesoft GmbH $ o_)$$$: 82-84 Mainzer Landstrasse ;$,_/\ &&:' 60327 Frankfurt Germany ' /( &&& \_' Email : [EMAIL PROTECTED] .Business Hours : +49 69 9757 200 &&&: ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing a list of projects
Robert Thorpe writes: > > My company has a CVS server with several(5) projects on it, in > order to access them I must be able to name them, I can't always > remember the name, In particular I can't remember which words > begin with capitals and which don't. Is there a way to list all the > projects in the repository? If they have entries in the modules file, you can use "cvs co -c". -Larry Jones TIME?! I just finished the first problem! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
