On Mon, Jul 09, 2001 at 04:12:30AM -0400, Greg A. Woods wrote:
[ On Monday, July 9, 2001 at 00:01:01 (-0400), Eric Siegerman wrote: ]
Well, with CVS the meaning of frozen file is quite a bit different.
In the most basic sense what I'm saying is that -kv should be the
default for cvs export.
[ On Wednesday, July 11, 2001 at 15:40:04 (-0400), Eric Siegerman wrote: ]
Subject: Re: The hated $Log$ keyword
On Mon, Jul 09, 2001 at 04:12:30AM -0400, Greg A. Woods wrote:
In the most basic sense what I'm saying is that -kv should be the
default for cvs export.
Ah, now I get
[ On Monday, July 9, 2001 at 00:01:01 (-0400), Eric Siegerman wrote: ]
Subject: Re: The hated $Log$ keyword
and that they contain their markers
when they appear in a frozen file.
Why is this a problem? I very much prefer it. Suppose, using
SCCS or raw RCS, I accidentally edit a file I
On , July 7, 2001 at 18:22:09 (+0100), James Youngman wrote:
Subject: Re: The hated $Log$ keyword
What if there was a keyword like $Log$ but which expanded to the
entire log history (with comment leaders)? This would avoid the
merge problem and surely cannot be too expensive to compute
[ On Sunday, July 8, 2001 at 20:13:40 (-0400), Eric Siegerman wrote: ]
Subject: Re: The hated $Log$ keyword
I thoroughly agree about $Log$, but:
- what's evil about the rest?
The evil thing abou RCS keyword design is that they contain their
values when stored in the ,v file
On Sun, Jul 08, 2001 at 10:39:52PM -0400, Greg A. Woods wrote:
The evil thing abou RCS keyword design is that they contain their
values when stored in the ,v file,
Mmm, yes. If it stripped out the values at commit time, and just
stored the keywords, all these *#(! merge conflicts would go
Richard Wesley [EMAIL PROTECTED] writes:
BTW, I appreciate the arguments against using $Log$ (redundancy,
merging, admin -m, etc.), but these guys really like the Header
Comments functionality they had with another system (MPW Projector)
so I'm trying to figure out what will work best for
[ On , July 7, 2001 at 18:22:09 (+0100), James Youngman wrote: ]
Subject: Re: The hated $Log$ keyword
What if there was a keyword like $Log$ but which expanded to the
entire log history (with comment leaders)? This would avoid the
merge problem and surely cannot be too expensive to compute
BTW, I appreciate the arguments against using $Log$ (redundancy,
merging, admin -m, etc.), but these guys really like the Header
Comments functionality they had with another system (MPW Projector)
Back in the 80's when I was starting with rcs I considered $Log$
entries to be cute at first. I
Hi all -
I am talking to some folks (both in house and at another company)
about $Log$ functionality, and I have some questions that I was
hoping someone could answer quickly:
- Is there a more detailed discussion of the problems than what
appears at
[ On Wednesday, May 2, 2001 at 10:39:47 (-0700), Richard Wesley wrote: ]
Subject: The hated $Log$ keyword
BTW, I appreciate the arguments against using $Log$ (redundancy,
merging, admin -m, etc.), but these guys really like the Header
Teach them to use cvs log (and even cvs rlog now
Greg A. Woods wrote:
[ On Wednesday, May 2, 2001 at 10:39:47 (-0700), Richard Wesley wrote: ]
Subject: The hated $Log$ keyword
BTW, I appreciate the arguments against using $Log$ (redundancy,
merging, admin -m, etc.), but these guys really like the Header
Teach them to use cvs log
12 matches
Mail list logo
