[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: history format

From: Mark D. Baushke
Subject: Re: history format
Date: Sun, 20 Aug 2006 22:04:50 -0700

Hash: SHA1

Mansour <address@hidden> writes:

> Hi : every body, I am starting with CVS, but I am having few issues,
> and confussion.
> The first issue is to understand the output lines of history command:

To really understand it, you may need to read the source.

> What are all these fields ?? I know the time the user, but why the
> +0000 and why the module name twice??
> O 2006-08-17 13:51 +0000 user module1       =module1=       <remote>/*

The +0000 is the timzeone for UTC (aka GMT). In some versions of CVS,
you might see your localtime timezone listed on the output, but cvs
normally tries to record everything in the UTC time so that global
development won't care if it is server or client time that is recorded.

For the 'O' record, the format is

    ISO-8601-format year-month-day hour:min +zone

cd /tmp
% cvs -d /tmp/foo.repository init
% cvs -d /tmp/foo.repository co -d top .
% cvs -d /tmp/foo.repository history
O 2006-08-21 04:55 +0000 mdb  =top= /tmp/*
% cvs -d /tmp/foo.repository rtag -b foo-branch CVSROOT
% cvs -d /tmp/foo.repository co -d foo-cvsroot -r foo-branch CVSROOT
% cvs -d /tmp/foo.repository history
O 2006-08-21 04:56 +0000 mdb [foo-branch] CVSROOT =foo-cvsroot= /tmp/*
O 2006-08-21 04:55 +0000 mdb         =top=         /tmp/*
% cvs -d /tmp/foo.repository release -d foo-cvsroot
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `foo-cvsroot': yes
% cvs -d /tmp/foo.repository history
O 2006-08-21 04:55 +0000 mdb  =top= /tmp/*
% cvs -d /tmp/foo.repository release -d top
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `top': yes
% cvs -d /tmp/foo.repository history

Similar things will happen when you are using :pserver: or :ext:, but
then the workdir is going to be <remote>.

Generally, I find that I don't really care about read operations on the
repository. I personally use LogHistory=TMAR as those records are
sometimes useful.

> The other issues. I started develping a project. However, once I get
> to a working state of the project I do and update "ONLY", to prevent
> from any mistakes in the future. Is there a way to go and retrieve
> these working states ???

Why does this matter?

> Let's say I was able to get one of these states, How can I remotely
> tag it ??

This is probably not possible. You would be more likely to find it
useful to do time-based checkouts or updates if that would be useful.

> Can any one help please ?? Any advice will be appreciated about how to
> achieve this easily the next time. I mean, If I want to save few
> changes, it doesn't make scence to do a release, so may be I will have
> to tag the files. Now are they taged automatically by date??

Not really. That is, there is no explict tag added to the repository.
You may do a time-based checkout, but if it is an important release,
then you should probably use an explict 'cvs tag' operation. You may
also wish to record more information via a loginfo or taginfo trigger
if you feel it is needed.

        -- Mark
Version: GnuPG v1.4.4 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]