-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander <[EMAIL PROTECTED]> writes:
> > I only create the ,foo.c, file - I don't write anything into it; the
> > existence of the file is enough to act as the RCS lock; if I can do my
> > inplace modification then I delete this file after doing it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> * Paul Sander ([EMAIL PROTECTED]) wrote:
>
> Hi Paul,
> Thanks for the reply,
>
> > Everything that Mark says is true. I'll add that some shops optimize
> > their read operations under certain
On Mar 20, 2005, at 3:54 PM, [EMAIL PROTECTED] wrote:
* Mark D. Baushke ([EMAIL PROTECTED]) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
OK, if I create a dummy ",foo.c," before
modifying (or create a hardlink with that name
to foo.c,v ?) w
* Mark D. Baushke ([EMAIL PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> >
> > OK, if I create a dummy ",foo.c," before
> > modifying (or create a hardlink with that name
> > to foo.c,v ?) would that be sufficient?
>
* Paul Sander ([EMAIL PROTECTED]) wrote:
Hi Paul,
Thanks for the reply,
> Everything that Mark says is true. I'll add that some shops optimize
> their read operations under certain conditions, and such optimizations
> would break if the RCS files are updated in-place.
>
> What happens is th
Hello,
I've tried both and found that normal (as opposed to vendor) branches
were easier to understand and not that difficult to implement ($Log$
turned out to be solvable just like other keywords), so that is what I
did.
Thanks much for all replies!
With kind regards,
Baurzhan.
On Sun, Mar 06
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> * Mark D. Baushke ([EMAIL PROTECTED]) wrote:
> Hi Mark,
> Thanks for your reply.
>
> > Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> >
> > > So - here are my questions/ideas - I'd appreci
Everything that Mark says is true. I'll add that some shops optimize
their read operations under certain conditions, and such optimizations
would break if the RCS files are updated in-place.
What happens is that, if the version of every file can be identified in
advance (using version number,
[Resend: I sent it with the wrong 'from' address - apologies
if you get both]
* Mark D. Baushke ([EMAIL PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
Hi Mark,
Thanks for your reply.
> Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
>
> > So - here are my questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> So - here are my questions/ideas - I'd appreciate comments to tell
> me whether I'm on the right lines:
> 1) As I understand it the tag data is the
> first of the 3 main data structures in the R
Hi,
I maintain a system that is used to hold a rather large
CVS repository (~1GB give or take) which could do with being faster.
Tagging in particular is slow and I don't think cpu or ram is the
issue (it is a dual xeon with 3GB of RAM).
My suspicion is that at least one of the problems is that
11 matches
Mail list logo
