bug-cvs
[Top][All Lists]
Advanced

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

Re: FW: Another bug in "admin -m"


From: Mark D. Baushke
Subject: Re: FW: Another bug in "admin -m"
Date: Sat, 18 Oct 2003 14:09:22 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodolfo Schulz de Lima <address@hidden> writes:

> > Oh well, at least we have fixed them now. Please let bug-cvs know if you
> > run into any more bugs in cvs.
> 
> Well, since you've mentioned that, I've a doubt, but I don't know if it's a
> bug or not. When you try to commit a file whose only thing that's changed is
> its timestamp, cvs doesn't do anything (even an error message isn't
> displayed), and the file remains marked as changed, i.e., CVS/Entries isn't
> updated to the timestamp of the file in repository. You need to do a cvs
> update -A <filename> to make the change. Is this the correct behavior,
> albeit a strange one? 

I don't believe I have never seen it happen myself.

> I've come into this when merging to the main branch a new version of a new
> version of a library in a vendor branch. When doing the import of the new
> version, all files are marked as "C", requiring me to do a merge to the main
> branch. When doing "cvs commit" to check in the merge, only the files with
> no change (but different timestamps) remains marked as changed.

I am not sure I understand. Can you write a simple test case (it can be
just a shell script) that demonstrates the problem?

If there is something in the CVS/Entries file that should be updated and
is not, then that probably is a bug that should be fixed.

Does doing a 'cvs update' fix the problem?

        Thanks,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/kawC3x41pRYZE/gRAkjRAKCl9PO/V30paz7/4AiYxhLNHEd4kACgnWO4
CgFTSutvD6hjks/g/XcTXaA=
=capY
-----END PGP SIGNATURE-----




reply via email to

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