Hi,
I have been trying to get a cvs log between revs that only shows log
messages for what has changed between revs. I've tried cvs log
-rrev1:rev2 and -rrev1::rev2. Both of which either show way too much
info or not enough. Where extra data is logs for files that have not
changed
Russ Sherk writes:
I have been trying to get a cvs log between revs that only shows log
messages for what has changed between revs. I've tried cvs log
-rrev1:rev2 and -rrev1::rev2. Both of which either show way too much
info or not enough. Where extra data is logs for files that have
If my repository is /usr/local/cvs, am I not supposed to be able to do
this:
cvs log /usr/local/cvs/project/file.py,v
I get the *PANIC* administration files missing error every time. There
is a CVS directory for that project. This command doesn't work on two
different machines in three
coach24 writes:
If my repository is /usr/local/cvs, am I not supposed to be able to do
this:
cvs log /usr/local/cvs/project/file.py,v
No, log is for use in a working directory; you want rlog. Most CVS
commands come in pairs -- foo and rfoo. foo is for use in a working
directory, rfoo
coach24 wrote:
If my repository is /usr/local/cvs, am I not supposed to be able to do
this:
cvs log /usr/local/cvs/project/file.py,v
I get the *PANIC* administration files missing error every time. There
is a CVS directory for that project. This command doesn't work on two
different
Larry,
I get a message about rlog being deprecated and it says no such
directory anyway.
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
/cvs, am I not supposed to be able to do
this:
cvs log /usr/local/cvs/project/file.py,v
I get the *PANIC* administration files missing error every time. There
is a CVS directory for that project. This command doesn't work on two
different machines in three different repositories
coach24 writes:
I get a message about rlog being deprecated and it says no such
directory anyway.
Then you have an ancient version of CVS -- you need to update.
-Larry Jones
I don't think that question was very hypothetical at all. -- Calvin
Bob McCallister wrote:
You misunderstood me. The librarian is presented with a screen that lists
all the projects. He clicks on a project and is presented with a list of
tags (in theory). He then chooses which tag and *then* the project is
checked out to its target directory.
I suppose
Ok, upgrading and using cvs rlog solved the problem. Thanks for
everyone's help.
Bob
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Jim Searle writes:
I found this question in the archives, but never saw an answer. Is there a
way to get 'BASE' to work with 'cvs log'?
Yes, by fixing the code, which I just did. :-)
The fix will be in the next releases. If you just can't wait, here's a
patch (for the stable [1.11] branch
I found this question in the archives, but never saw an answer. Is there a
way to get 'BASE' to work with 'cvs log'?
Thanks,
jim
From: Slawomir Nowaczyk
Subject:Equivalent to cvs log -rBASE::HEAD?
Date: Wed, 29 Sep 2004 17:57:49 +0200
Hello,
I would like to see cvs log messages
Hi,
cvs log -S -d 24 hours ago
works fine for me. It gave me the log of changes made 24 hours ago on the
CVS repository.
Thank you
Pradeep Kumar T
:
mic.co.in Subject: Re: using cvs log like
cvs log -d 24 hours ago
27-01-05 05:08
Hi,
i need to get the CVS log entries for entries made in the last 24 hours!
i tried
using cvs log like cvs log -d 24 hours ago
it doesnt work.
Any alternative?
Thanks and Regards.
Pradeep Kumar T
[EMAIL PROTECTED] wrote:
Hi,
i need to get the CVS log entries for entries made in the last 24 hours!
i tried
using cvs log like cvs log -d 24 hours ago
it doesnt work.
Any alternative?
cvs log does not work as I expect, but it can be made to give what you want.
try
cvs log -S -d 24
I'm running cvs version 1.11.17 on a Sun E250 Solaris 9 and can't seem
to get logs by date working.
$ cvs --version
Concurrent Versions System (CVS) 1.11.17 (client/server)
If I issue the comand
$ cvs log -d =20041120
I am returned with log information for all files in the directory. Here
Scott Watters writes:
$ cvs log -d =20041120
I am returned with log information for all files in the directory.
Correct. The -d option only affects which log messages get displayed,
you still get headers for all the files. If you don't want the extra
headers, you need the -S option, too
DOH!!
I've been staring at the mole book and man page for hours. I have no
idea how I glossed over that option.
Sorry for the waste of bandwidth.
Scott
On Mon, 2005-01-10 at 17:05 -0500, Larry Jones wrote:
Scott Watters writes:
$ cvs log -d =20041120
I am returned with log
[ On Tuesday, October 5, 2004 at 18:41:59 (+0200), Slawomir Nowaczyk wrote: ]
Subject: Re: Equivalent to cvs log -rBASE::HEAD?
Note if it did work, then you would only need cvs log -rBASE::.
Specifying HEAD would be meaningless (and perhaps also misleading
since it is defined as simply
. So:
I know the code I have in my workspace. But then I want to make cvs
update. I would like to know, however, what is going to change - and
not just filenames, but the log entries... for all the commits which
happened between my last update and now.
Something like cvs log -rBASE::HEAD looks
between my last update and now.
Something like cvs log -rBASE::HEAD looks perfect, and has only one
single flaw: doesn't work.
Well, what about cvs diff -uN -r HEAD? I have not tested if it works at
all, and it would not give you the log but the complete diff, but it
might be a partial solution
commits which happened between my last update and now.
Slawomir Something like cvs log -rBASE::HEAD looks perfect, and has only
Slawomir one single flaw: doesn't work.
Slawomir Any idea how else could I accomplish what I want?
If you are interested, I could help you write a Perl script using
On Tue, 05 Oct 2004 13:27:36 +0200
Spiro Trikaliotis [EMAIL PROTECTED] wrote:
# Well, what about cvs diff -uN -r HEAD? I have not tested if it
# works at all, and it would not give you the log but the complete
# diff, but it might be a partial solution to your problem?
Yes, I can make diff to
Hello,
I would like to see cvs log messages for all the files and revisions
which will be updated by next cvs update command -- to get an idea
as to what has been changed.
Ideally, I would like to do cvs log -rBASE::HEAD
But log -r switch only accepts revisions, not tags (according
Hi,
when I work with different WIN Clients I get weird characters when
checking the history
cvs log file
รท-02 14:11:45 +; author: xx; state: Exp;
Thats leads to problem with Clients like WinCVS or tortiose so that
they could not determine the Date correct.
The same on a UNIX System
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Georg,
Georg Bischof [EMAIL PROTECTED] writes:
when I work with different WIN Clients I get weird characters when
checking the history
cvs log file
-02 14:11:45 +; author: xx; state: Exp;
Thats leads to problem with Clients like
Hi,
I have a file that I'm getting an abort from cvs log on in my
repository.
$ cvs log
appspack/oracle/ig/modules/ar/install/sql/obtig_ar_filter_pb.sql
cvs [log aborted]: unrecognized operation '\x73' in
/export/cvs/prodops/appspack/oracle/ig/modules/ar/install/sql/obtig_ar_f
Carter Thompson writes:
What's the best way to go about resolving this error? I've tried to
find problems
directly with the RCS file itself but I've been unable to find anything
wrong with
it and I'm afraid that I'm missing something obvious.
That error does, indeed, mean that the RCS
I'm using cvs log to aggregate logs of what has gone into a specific
build (determined by datespec). I'm only interested in one branch at a
time. The log invocation is something like this:
cvs -q log -N -r$BRANCH -d $DATE1$DATE2
The problem is that if a file doesn't exist on $BRANCH (like
Tyler writes:
The problem is that if a file doesn't exist on $BRANCH (like it was
added to the trunk sometime after the branch was cut), cvs log returns
that file's entire history.
You need to update your (server) CVS -- that bug was fixed long ago.
-Larry Jones
Mom must've put my cape
Ramanuj Singh wrote:
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
Please do not post MIME-encoded messages to this list
How to see logs of tags and branches in project
cvs log
to know who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop wrote:
and when the branch or tag was done.
CVS does not keep track of when tags or branches are applied. You might be
able to track that using the taginfo script. See
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_18.html#SEC175 for
Title: cvs log for tag and branches
How to see logs of tags and branches in project to know who is the owner of branch and tag and when the branch or tag was done.
The information transmitted is intended only for the person or entity to whom it is addressed and may contain confidential
Derek Robert Price wrote:
Mark D. Baushke wrote:
a bigger question is if that change should also go into
things like $Id$
and other RCS keyword expansion strings...
Got me here. I tend to avoid RCS keywords as much as
possible. I know
that they are useful via the `ident' command,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop wrote:
Seems to me the best way to implement this would be to have a global option
which controls the date format, something like:
-l Display local time for timestamps
-u Display UTC for timestamps
Maybe. I think I would prefer
Title: Message
I have been asked to
"fix" this by my boss: cvs log returns the timestamp of the file in Coordinated
Univeral Time. All other ways of looking at the timestamp return it in
local time. Is there any quick, elegant way to get cvs log to display the
date in local time?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Blaney, Liza wrote:
Message
I have been asked to fix this by my boss: cvs log returns the
timestamp of the file in Coordinated Univeral Time. All other ways of
looking at the timestamp return it in local time. Is there any quick,
elegant way
Blaney, Liza writes:
This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
I have been asked to fix this by my boss: cvs log returns the
timestamp of the file in Coordinated Univeral Time. All other ways
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek Robert Price wrote:
I've considered this problem before but have never had the time to
implement the solution. The most correct way I have come up with is
to add a tagged text type to the client/server protocol using the MT
response type.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones wrote:
I have been asked to fix this by my boss: cvs log returns the
timestamp of the file in Coordinated Univeral Time. All other ways of
looking at the timestamp return it in local time. Is there any quick,
elegant way to get cvs log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Blaney, Liza [EMAIL PROTECTED] writes:
I have been asked to fix this by my boss:
Summary: It is not a bug and does not need to be fixed.
(See also the advice for engineers to a PHB via the Dilbert.com site.)
cvs log returns the timestamp
I use change logs generated by cvs2cl.pl http://www.red-bean.com/cvs2cl
and the XSLT transformation from
http://www-106.ibm.com/developerworks/library/us-gentoo4, all of which
produces very useful HTML, with the advantage that I can set the time
zone to whatever I want for different HTML reports.
.)
This is debatable.
cvs log returns the timestamp of the file in Coordinated Univeral
Time.
This is correct.
All other ways of looking at the timestamp return it in local time.
I believe you to be mistaken. Could you please cite examples? I do not
believe that cvs will ever OUTPUT time in localtime
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Doar wrote:
If your boss wants to see local timestamps on cvs output, that's much
more work, as others have pointed out.
I still say there are only two minor edits that would need to be made to
the CVS source. Three if you want to include
for engineers to a PHB via the Dilbert.com site.)
This is debatable.
So it seems. :-)
cvs log returns the timestamp of the file in Coordinated Univeral
Time.
This is correct.
All other ways of looking at the timestamp return it in local time.
I believe you to be mistaken. Could you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark D. Baushke wrote:
Derek Robert Price [EMAIL PROTECTED] writes:
I have a minor quibble, the timezone should be numeric - rather than
the alphabetic UTC. However, I agree that a timezone indication in the
output of cvs log and friends
indication in the
output of cvs log and friends would be reasonable.
Um, yes. If I'd thought about the matter more I probably would have
suggested the same thing.
In fact, I suggest that movement to ISO 8601 format for output would be
desirable. That is,
ISO 8601 format -dd-mm
Mark D. Baushke writes:
ISO 8601 format -dd-mm hh:mm:ss -
You've got the mm and dd swapped, it's -mm-dd hh:mm:ss -.
-Larry Jones
The hardest part for us avant-garde post-modern artists is
deciding whether or not to embrace commercialism. -- Calvin
Of Derek
Robert Price
Sent: Wednesday, March 24, 2004 4:46 PM
To: Mark D. Baushke
Cc: Liza Blaney; [EMAIL PROTECTED]
Subject: Re: cvs log and UTC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark D. Baushke wrote:
Derek Robert Price [EMAIL PROTECTED] writes:
I have a minor quibble
--- Forwarded mail from [EMAIL PROTECTED]
Derek Robert Price [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
The `cvs log' output is definately not designed to be machine
parsable, as you would likely know if you have ever tried to parse it.
I have many thounsands of lines of perl, gawk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander [EMAIL PROTECTED] writes:
There should be little need to parse the output of cvs log or cvs rlog
if you have access to the server and can run rinfo on the RCS files. It
produces output that's designed to be machine readable. Sources
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones [EMAIL PROTECTED] writes:
Mark D. Baushke writes:
ISO 8601 format -dd-mm hh:mm:ss -
You've got the mm and dd swapped, it's -mm-dd hh:mm:ss -.
Yes. Mea culpa. I cut-n-pasted a line from src/sanity.sh which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark D. Baushke wrote:
In fact, I suggest that movement to ISO 8601 format for output would be
desirable. That is,
ISO 8601 format -mm-dd hh:mm:ss -
vs
cvs log's format of '/mm/dd hh:mm:ss'
[I corrected the ISO 8691 format
thanks a lot. Will try that.
Benno
[EMAIL PROTECTED] (Pierre Asselin) wrote in message news:[EMAIL PROTECTED]...
benno.loeffler [EMAIL PROTECTED] wrote:
I would like to start a contiuous-build whenever something was
committed to a particular module in our cvs repository (which is
hosted
All;
I am trying to find out the file name and revision number of every file that is
tagged by a release tag. My first thought is to use the log command and parse the
output. So I type: cvs log -rTAG_NAME -sRel MY_Directory enter . My reasons for
the options are: -rTAG_NAME - I only
[EMAIL PROTECTED] writes [in one very long line]:
I am trying to find out the file name and revision number of every
file that is tagged by a release tag. My first thought is to use the
log command and parse the output. So I type: cvs log -rTAG_NAME -sRel
MY_Directory enter .
See
Sorry to spam everyone. After a detailed investigation I found the log message
works correctly using cvs 1.11.5, but I also found that I cannot use log to
identify all changes between two tags. I am trying to identify All changes by
using -- cvs log -rus-1-0-9-78::us-1-0-9-80 -- I have
From: Larry Lords [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 9:04 AM
To: [EMAIL PROTECTED]
Subject: Re: cvs log problem
Does anyone know how to identify ALL changes between two tags?
Larry Lords
cvs rdiff -s -rtag1 -rtag2 module
This will give results
Sorry to trouble you with this question, but I hope
some of you gurus already know the answer.
When I use the following command I get every file
listed in the module regardless of whether or not I
changed them, which is bad,
cvs log -b -d 2003-03-18 02:40 -wrjocham
jboss-3.0.6_tomcat
Ralph Jocham writes:
When I add the -S option I only get the files I
modified listed, which is good. However, I also only
get those in the root directory of the module (i.e.
not in the subdirectories), which is bad.
There is nothing in the -S option that prevents recursion -- if you're
not
I am seeing some of the same problems. There are times it seems to work, and
other times I just get the root directory files.
Is there a way of getting the latest version for a window's cvs client without
downloading the source and building it from scratch? I believe it is my CVSNT
client that
I just upgraded by windows system from CVSNT 2.0.4(?) to cvs 1.11.5 and the log
appears to be working correctly now. I will do some more detail checking, but
it looks good.
Larry Lords
+++
I am seeing some of the same problems. There are times it
Larry Lords writes:
Is there a way of getting the latest version for a window's cvs client without
downloading the source and building it from scratch? I believe it is my CVSNT
client that could be some of the problem.
There are binaries on cvshome.org, but it appears that Derek hasn't
MacDonald, Ian writes:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary91921517666352637==
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
Shouldn't cvs simply be using read locks while executing the log
command?
It
Title: RE: Lock contention executing cvs log
Thanks Larry,
Sorry for the MIME post. I realized that I forgot to turn it off after sending it (and you can't un-send a message).
Not sure if you saw my follow up. But I'm now thinking that the lock contention is not the source of my
Title: RE: Lock contention executing cvs log
(Hopefully this time at plain-text) - Sorry again
Thanks Larry,
Sorry for the MIME post. I realized that I forgot to turn it off after sending it (and you can't un-send a message).
Not sure if you saw my follow up. But I'm now thinking
MacDonald, Ian writes:
While several of my build processes were running, I was monitoring the CVS
server with 'top'. I noticed a strange occurrence with two of cvs processes
that were currently executing a log command - both processes grew to consume
nearly all available memory (in my case
Title: Lock contention executing cvs log
Hi Folks,
I'm sorry if this posting might appear twice. I first posted this to the NNTP group gnu.cvs.help but was not sure my posts were actually making it.
Here's my problem:
We have an automated build environment (CruiseControl) running
27, 2003 12:10 PM
To: '[EMAIL PROTECTED]'
Subject: Lock contention executing cvs log
Hi Folks,
I'm sorry if this posting might appear twice. I first posted this to the
NNTP group gnu.cvs.help but was not sure my posts were actually making it.
Here's my problem:
We have an automated build
Hiya
When using cvs log filename does anyone know where this function is called
from and when the actual log information is retrieved from.
I know it has something to do with loginfo file in cvsroot/CVSROOT
but cant see where it retrieves the log info from exactly.
Thanx
(this info)
RCS file
Hiya
When using cvs log filename does anyone know where this function is called
from and when the actual log information is retrieved from.
The function exists within CVS, and it retrieves the log information from
the file in the repository.
I know it has something to do with loginfo
Is there a way to ignore the no revision warning message when using the
cvs log command? I am using a CVS build that I checked out from around
11/11/02 timeframe to use the new cvs log -r tag1::tag2 syntax. But
if tag1 does not exist in the file (e.g., a new file that was added),
CVS currently
(see http://www.cvsnt.com/).
cvs server: Logging .
cvs [server aborted]: linefeed expected in C:/cvsrepo/test/file.c,v (got 13)
I think that the problem is obvious and I have read several mails
describing the same
problem:
The windows use CRLF instead of the LF that the cvs log requires
Apostolos Manolitzas writes:
As far as I understand from the info pages of cvs (Where files are
stored within the repository )
the files are stored in RCS format which doesn't mean that are in binary
form.
Yes, it does. RCS files are *NOT* plain text files -- they may contain
arbitrary
Hello everybody,
I use cvs 1.11.1p1 in my Linux box (RH7.1). The linux box is the client
and the server
uses cvsnt (win2000) on a windows machine.
I am having a problem with the logging. When I try to do cvs log file
the server responds
with:
cvs server: Logging .
cvs [server aborted
/).
cvs server: Logging .
cvs [server aborted]: linefeed expected in C:/cvsrepo/test/file.c,v (got 13)
I think that the problem is obvious and I have read several mails
describing the same
problem:
The windows use CRLF instead of the LF that the cvs log requires.
That should be irrelevant
Hi
there
I am wondering
whether there is a way to require a certain cvs log format --per branch--, not
per module.
For example, I want
to require a format like "bugnr: digits" in my release branch, but not
in the main branch.
The documentation
about the "verifymsg
Myke Olson writes:
Is there a way to force the log to begin with a blank line? I liked it
better the old way. :)
Set up rcsinfo to point to a template file with a blank line in it.
-Larry Jones
The authorities are trying to silence any view contrary to their own!
-- Calvin
Use cvs rdiff -s to get a summary of the changes between the two
tags, and then parse its output and use rlog to retrieve the log
messages for the indicated revisions of the indicated files.
Check out URL:http://www.mit.edu/~jik/cvsrdiffsum, which will do
this for you automatically and produce a
Title: How to get Log messages between two tags usind cvs log command?
Hi,
There is an option of getting log message between two dates (-d) , between two revisions (-r).
Does anybody know how to get log messages between two tags on the same branch.
I want to prepare a changelog file
Shailesh Garg writes:
This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE.
There is an option of getting log message between two dates (-d) ,
between two revisions (-r).
Does anybody know how to get
Use cvs rlog
-Original Message-
From: Neil Zanella [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 7:52 PM
To: [EMAIL PROTECTED]
Subject: cvs log question
Hello,
Is there a way to look at a log file without first checking out?
Thanks,
Neil
Neil Zanella writes:
Is there a way to look at a log file without first checking out?
CVS 1.11.1 and newer have an rlog subcommand to do that.
-Larry Jones
These findings suggest a logical course of action. -- Calvin
___
Info-cvs mailing list
Hello,
Is there a way to look at a log file without first checking out?
Thanks,
Neil
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
This has probably been done a thousand times before, but I wrote a simple CVS
log parser to get more 'user friendly' output. Especially, output is filtered
when number of selected revisions is 0 (I think someone requested this a while
ago).
source code (MSVC6, gcc 2.95.2) and Win32 executable
This is a weird one, and I coulda sworn this worked for me last week. I
can no longer run 'cvs log file.c' in my local repository and see a list
of the tags that file.c exists within. I was under the impression that
'cvs log' would display tags. What am I doing wrong here?
As an aside
David A. Desrosiers writes:
This is a weird one, and I coulda sworn this worked for me last week. I
can no longer run 'cvs log file.c' in my local repository and see a list
of the tags that file.c exists within. I was under the impression that
'cvs log' would display tags. What am I doing
Maybe you want cvs_status -v filename
Jeanie
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
I have a module with lots of old branches and lots of revisions. Is there
anyway for me to follow the branches and figure out which ones were merged
into the truck, and which ones were not? Through cvs log?
to give a real world example, as a qa person, I am responsible for assigning
release
Matthew Herrmann writes:
since it would be used pretty commonly -- shame -rTAG1::TAG2 doesn't do what
people would expect it to do.
Would anyone object to changing it so that it does revisions after TAG1
and not after TAG2 rather than after TAG1 and before TAG2 (e.g.,
currently it is
[ On Tuesday, January 8, 2002 at 13:00:19 (-0500), Larry Jones wrote: ]
Subject: Re: request for log option to specifically exclude the first tag,
workaround for cvs log -r -r
Matthew Herrmann writes:
since it would be used pretty commonly -- shame -rTAG1::TAG2 doesn't do what
people
to specifically exclude the first
tag, workaround for cvs log -r -r
Matthew Herrmann writes:
since it would be used pretty commonly -- shame -rTAG1::TAG2 doesn't do
what
people would expect it to do.
Would anyone object to changing it so that it does revisions after TAG1
and not after TAG2 rather than
Matthew Herrmann writes:
just to clarify, it should include TAG2 only in the case where a tag does
not exist for TAG1...
Right. If TAG1 and TAG2 are both attached to the same revision, the
revision specified by TAG2 would not be *after* the revision specified
by TAG1 and thus would not be
the dates of the two
logs, and then do a cvs log from just after the last committed date/time of
the first tag, and up to and including the date/time of the last file
containing the second tag. But that won't be sufficient if you're using
branching -- you'll then need to ensure that you're only getting
that
recent discussions about dates inspired me on: find the dates of the two
logs, and then do a cvs log from just after the last committed date/time of
the first tag, and up to and including the date/time of the last file
containing the second tag. But that won't be sufficient if you're using
branching
I did find out what problem was. Since I was using vim (or gvim) which
forked out a separate window, for some reason CVS assumed I had completed
typing the log message, even before I actually typed in anything. So now vim
does not fork out a separate process.
Not sure if this is a bug or not,
I am using CVS on HP-UX 11.00. I use CVS in the bash shell. The CVS version
is 1.10.8. When I cvs commit a file, it brings up the vi editor and asks me
to put my comments in, which I do. Then it prompts me saying that the log
message is empty and if I want to continue or not. Why is not the log
On Wed, Dec 19, 2001 at 12:21:34PM -0500, Jeremiah wrote:
I am using CVS on HP-UX 11.00. I use CVS in the bash shell. The CVS version
is 1.10.8. When I cvs commit a file, it brings up the vi editor and asks me
to put my comments in, which I do. Then it prompts me saying that the log
message
Ville Herva wrote:
Urmhh, I should have just deleted the sentence as it is clear I was unable
to write it unambiguosly.
To reiterate, this is what I ment:
even you could cook up the patch: you = me, Ville Herva, the author of
_this_ and the
1 - 100 of 156 matches
Mail list logo
