[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: how to identify a release
From: |
Alexander Kamilewicz |
Subject: |
Re: how to identify a release |
Date: |
Wed, 13 Jun 2001 15:18:18 -0500 |
Matthew Riechers wrote:
>
> Andreas Wolff wrote:
> >
> > I want to identify a release of my source.
> >
> > I understood that the tag mechanism can be used for this purpose. But in
> > this case I have to apply the tag to each file. I am afraid that in big
> > projects with lots of files this may take a reasonable amount of time.
> >
> > Is there a better (faster) way to identify a release?
> >
>
> Not via cvs commands. Tagging takes roughly the same amount of time as
> other operations. If it seems too slow, try a faster machine. In my
> case, the entire file system is hosted via NFS, so I usually use a
> system with a local disk for tagging. That speeds things up immensely.
> Even though tagging is done on the repository machine, the communication
> back to the client slows things down. Perhaps redirecting stdout to
> /dev/null or a log could help.
Or even "-Q". :P
Yep, tagging can take time. Best to do it on a local filesystem, as
Matt says.
Look at it as a good way to get a coffee break.
:)