History of the project

[KalliMan]

Hi there,

when I run this command:

"cvs history ProccessView"
the result looks like is:

O 2009-07-19 17:04 +0000 KalliMan
=.= localhost/*
O 2009-07-11 22:00 +0000 KalliMan ./ApiDialogsClient =./
ApiDialogsClient= localhost/./ApiDialogsClient
O 2009-07-11 15:31 +0000 KalliMan ./KUtilities =./
KUtilities= localhost/./KUtilities
O 2009-07-11 15:36 +0000 KalliMan ./KUtilities/Bin =./
KUtilities/Bin= localhost/./KUtilities/Bin
O 2009-07-11 21:51 +0000 KalliMan ./test =./
test= localhost/./test
.....

Can somebody tells me what the ... is the meaning of these columns???

[Arthur Barrett]

Post by KalliMan
"cvs history ProccessView"

.
.
.

Post by KalliMan
Can somebody tells me what the ... is the meaning of these columns???

http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_16.html#SEC144

Remember that the history file is not failsafe (if there is any problem
writing to the history then cvs silently continues), so it's not a
guarenteed history of your project. CVSNT (GPL/free runs on Linux,
windows etc just like CVS) has a failsafe audit for this reason - but
you can also use 'cvs rlog' to scour each RCS file for the history in
CVS 1.11 or 1.12.

Regards,


Arthur Barrett

[Amaresh Ch Das]

Hi ,

 O 2009-07-19 17:04 +0000 KalliMan =.=                            Â

[KalliMan]

have a look my processview :- (remote server)

cvs history ProccessView
Password:
O 2009-07-13 10:58 +0000 amareshcd kernel-2.6   =kernel-2.6=   <remote>/*
O 2009-07-13 12:54 +0000 amareshcd libadapt     =libadapt=     <remote>/*


Have a look this command “ls -ltr “ you will get good idea.


Have a look for more “http://ittipsandtrics.blogspot.com”

Thanks,
-Amaresh




Thanks,
-Amaresh

&uarr; Grab this Headline Animator


--- On Sun, 19/7/09, KalliMan <***@gmail.com> wrote:

From: KalliMan <***@gmail.com>
Subject: History of the project
To: info-***@nongnu.org
Date: Sunday, 19 July, 2009, 11:35 PM

Hi there,

when I run this command:

"cvs history ProccessView"
the result looks like is:

O 2009-07-19 17:04 +0000 KalliMan
=.=                              localhost/*
O 2009-07-11 22:00 +0000 KalliMan ./ApiDialogsClient     =./
ApiDialogsClient=      localhost/./ApiDialogsClient
O 2009-07-11 15:31 +0000 KalliMan ./KUtilities                =./
KUtilities=                localhost/./KUtilities
O 2009-07-11 15:36 +0000 KalliMan ./KUtilities/Bin          =./
KUtilities/Bin=           localhost/./KUtilities/Bin
O 2009-07-11 21:51 +0000 KalliMan ./test                       =./
test=                        localhost/./test
......

Can somebody tells me what the ... is the meaning of these columns???





Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/
--0-1390209397-1248159939=:37580
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi , <br><br>&nbsp;O 2009-07-19 17:04 +0000 KalliMan =.=&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-weight: bold;"> localhost</span>/*<br>

[Larry Jones]

Post by Arthur Barrett

Post by KalliMan
Can somebody tells me what the ... is the meaning of these columns???

http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_16.html#SEC144

Unfortunately, that section does *not* document the format of the
history output (although it should).

[Arthur Barrett]

Larry,

Post by Larry Jones

Post by Arthur Barrett

Post by KalliMan
Can somebody tells me what the ... is the meaning of these columns???

http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_16.html#SEC144

Unfortunately, that section does *not* document the format of the
history output (although it should).

I thought all the columns except the 'type' column were self explanatory, and that page explains the record type column pretty well. So yes I interpreted the question to be not 'what is the precise definition and meaning of each and every column?', but rather as 'what is the meaning of the unobvious column?' - and maybe a little of 'where is the manual for this confounded thing?'.

It could be argued that the section should also explain a lot of other things about history, including that it's not failsafe, that the history is not created automatically (not only does the CVSROOT/history file need to exist to run the history command it must exist before history is recorded), the meaning of each column, how to configure which command types are listed by default etc etc. But the page for the 'log' command doesn't explain the output of 'log' either, so if the manual is currently unhelpful then at least the manual is consistently unhelpful:
http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs_16.html#SEC150

My suspicion has always been that the original idea for the manual was that each thing should only be documented in one place (easier to change later that way) - and since the output of history is more-or-less the stored format of history I think that's the only place it gets documented. I did think I saw a link to the administration files section of the manual from the history command page, but on closer inspection there does not appear to be such a link...

Regards,



Arthur

[Larry Jones]

Post by KalliMan
Can somebody tells me what the ... is the meaning of these columns???

Here's what I've just added to the manual:

A.13.2 history output
---------------------

`history' prints a line for each selected history record. Each line
begins with a character indicating the record type (*note history
options::), followed by a timestamp (in the format `YYYY-MM-DD HH:MM
ZZZZ'), then the name of the user who performed the action. The
remainder of the line depends on the record type:

`T'
The relative path to the directory in the repository; then the
description of the tag in the format `[NAME:OPT]' where NAME is
the tag name and OPT is `D' for `tag -d', the specified revision
for `tag -r', the specified date for `tag -D', or `A' for a plain
`tag'.

`F', `E', `O'
The tag/revision/date checked out, if any, enclosed in `[' and `]';
the relative path to the directory in the repository, if any; the
associated module name, enclosed in `=' and `='; then the absolute
path to the local working directory or `<remote>'.

`W', `U', `P', `C', `G', `M', `A', `R'
The revision checked out; the file name; the relative path to the
directory in the repository, if any; the associated module name,
enclosed in `=' and `='; then the absolute path to the local
working directory or `<remote>'.


`~' at the beginning of a working directory means the user's home
directory. `*' at the end of a repository or working directory means
the associated module name.

A.13.3 history examples
-----------------------

$ cvs history -e

A 2009-07-21 20:21 +0000 bach 1.1 tc.1 yoyodyne/tc/man == ~/tc/man
M 2009-07-21 20:22 +0000 bach 1.2 backend.c yoyodyne/tc == ~/tc
M 2009-07-21 20:27 +0000 bach 1.5 frontend.c yoyodyne/tc == ~/tc
T 2009-07-21 20:27 +0000 bach yoyodyne/tc [rel_0_3:A]
O 2009-07-21 20:28 +0000 cedar [rel_0_1] yoyodyne/* =tc= <remote>/*
C 2009-07-21 20:29 +0000 cedar 1.3 driver.c yoyodyne/tc == <remote>
U 2009-07-21 20:29 +0000 cedar 1.5 frontend.c yoyodyne/tc == <remote>
F 2009-07-21 20:31 +0000 bach =yoyodyne= ~/*
E 2009-07-21 20:33 +0000 bach [rel_0_3] yoyodyne/tc =.= /foo/*
O 2009-07-21 20:37 +0000 bach yoyodyne/* =tc= ~/*
R 2009-07-21 20:37 +0000 bach 1.2 test2.t yoyodyne/tc/testing == ~/tc/testing
E 2009-07-21 20:38 +0000 bach [2009.07.21.20.38.48] yoyodyne/* =tc= /foo