CVS log

CVS log

[Luc Teirlinck]

Is there a reasonably easy way to correct the per file CVS log entry
for an already committed change?  I inadvertently forgot a per file
entry for a recent change to Makefile.in.  I do not know how important
this is.  The change is properly documented in the Change Log.

I am just talking about:

(install-arch-indep, uninstall): Add SES manual.

Sincerely,

Luc.

Re: CVS log

[Stefan Monnier]

>>>>> "Luc" == Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Is there a reasonably easy way to correct the per file CVS log entry
> for an already committed change?  I inadvertently forgot a per file

Use PCL-CVS's `l' command to get the log and then hit `e'
(or M-x cvs-mode-edit-log) on the log entry you want to change.


        Stefan

Re: CVS log

[Andreas Schwab]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> Is there a reasonably easy way to correct the per file CVS log entry
> for an already committed change?  I inadvertently forgot a per file
> entry for a recent change to Makefile.in.  I do not know how important
> this is.  The change is properly documented in the Change Log.

The only way to change a CVS log entry is to edit the repository.  The
cvs frontend does not allow that.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: CVS log

[Stefan Monnier]

> The only way to change a CVS log entry is to edit the repository.  The
> cvs frontend does not allow that.

cvs admin -m<rev>:<msg> <file>


        Stefan

Re: CVS log

[Andreas Schwab]

"Stefan Monnier" <monnier@IRO.UMontreal.CA> writes:

>> The only way to change a CVS log entry is to edit the repository.  The
>> cvs frontend does not allow that.
>
> cvs admin -m<rev>:<msg> <file>

Yes, you're right, I missed that.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: CVS log

[Luc Teirlinck]

   cvs admin -m<rev>:<msg> <file>

I tried that, as both you and Andre Spiegel mentioned.  (I am not
familiar with pcl-cvs, although I could of course learn it if I would
need more specialized stuff than VC supports on a regular basis.)  I
usually use VC for all my RCS and CVS stuff.  This means that I am not
really used to command line CVS either.

I tried:

[bash2.05b.0 ~ 3 1] cd emacscvsdir/emacs
[bash2.05b.0 ~/emacscvsdir/emacs 3 2] cvs admin -m1.283:'(install-arch-indep, uninstall): Add SES manual.' Makefile.in
Enter passphrase for RSA key 'teirllm@swt40.swt.com': 
cvs [server aborted]: usage is restricted to members of the group anoncvs
[bash2.05b.0 ~/emacscvsdir/emacs 3 3] 

(My Emacs CVS stuff is in ~/emacscvsdir.)
Does that mean that I did something wrong or that one needs more than just
"regular" write access to the CVS to do this?

Sincerely,

Luc.

Re: CVS log

[Eli Zaretskii]

> Date: Fri, 12 Sep 2003 14:19:01 -0500 (CDT)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
> 
> I tried:
> 
> [bash2.05b.0 ~ 3 1] cd emacscvsdir/emacs
> [bash2.05b.0 ~/emacscvsdir/emacs 3 2] cvs admin -m1.283:'(install-arch-indep, uninstall): Add SES manual.' Makefile.in
> Enter passphrase for RSA key 'teirllm@swt40.swt.com': 
> cvs [server aborted]: usage is restricted to members of the group anoncvs
> [bash2.05b.0 ~/emacscvsdir/emacs 3 3] 

This works for me.

> Does that mean that I did something wrong or that one needs more than just
> "regular" write access to the CVS to do this?

I think you need to be a "Project Admin" for that, but please ask
cvs-hackers and savannah-hackers about this, to be sure.

Several maintainers, including myself, are defined as admins, so any
one of them can make this change for you.

Re: CVS log

[Miles Bader]

"Eli Zaretskii" <eliz@elta.co.il> writes:
> I think you need to be a "Project Admin" for that, but please ask
> cvs-hackers and savannah-hackers about this, to be sure.

Really?  I've used this command on emacs' cvs tree in the past, though
that may have been pre-savannah.

-miles
-- 
We have met the enemy... and he is us.  -- Pogo

Re: CVS log

[Eli Zaretskii]

> From: Miles Bader <miles@gnu.org>
> Date: 13 Sep 2003 21:54:21 +0900
> 
> "Eli Zaretskii" <eliz@elta.co.il> writes:
> > I think you need to be a "Project Admin" for that, but please ask
> > cvs-hackers and savannah-hackers about this, to be sure.
> 
> Really?

That's my interpretation of the fact that the command worked for me,
but not for Luc.  But if that command works for you now, my theory is
false.  I cannot find any other perinent privileges on savannah that
could have explained the difference, though.

Re: CVS log

[Miles Bader]

"Eli Zaretskii" <eliz@elta.co.il> writes:
> That's my interpretation of the fact that the command worked for me,
> but not for Luc.  But if that command works for you now, my theory is
> false.

It worked for me in the past, but I haven't used it for quite a while,
so who knows.

-Miles
-- 
"Most attacks seem to take place at night, during a rainstorm, uphill,
 where four map sheets join."   -- Anon. British Officer in WW I

Re: CVS log

[Luc Teirlinck]

Eli Zaretskii wrote:

   I cannot find any other perinent privileges on savannah that could
   have explained the difference, though.

The problem was that I did not have the "enable cvs admin commands"
checkbox checked in my account information, as Mathieu Roy pointed out
to me.  Everything worked fine after that.

Sincerely,

Luc.