* bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found
@ 2008-12-30 7:53 ` Sven Joachim
2008-12-30 10:16 ` Dan Nicolaescu
2008-12-30 10:55 ` bug#1740: marked as done ([era eriksson] vc.el adds new files at v2.1 if other v2.x file found) Emacs bug Tracking System
0 siblings, 2 replies; 3+ messages in thread
From: Sven Joachim @ 2008-12-30 7:53 UTC (permalink / raw)
To: bug-gnu-emacs
[-- Attachment #1: Type: text/plain, Size: 199 bytes --]
I'm revising old bugs reported against Emacs in Debian and will forward
some of them here that are still reproducible in current Emacs CVS.
This one is an example of a very well written bug report.
[-- Attachment #2: Type: message/rfc822, Size: 3587 bytes --]
From: era eriksson <era@iki.fi>
To: submit@bugs.debian.org
Subject: Bug#149196: emacs20: vc.el adds new files at v2.1 if other v2.x file found
Date: Thu, 06 Jun 2002 14:20:13 +0300
Message-ID: <E17FvJN-00031e-00@there>
Package: emacs20
Version: 20.7-2
Severity: normal
It seems that the version control mode vc.el has a "feature" with CVS
which causes it to check in new files beginning at version number 2.1
if there is another file whose version number is 2.x in the same
directory (i.e. CVS module / project).
I had been noticing this more and more frequently over time, but
hadn't been able to diagnose it correctly. Now here are the steps to
repro this.
* Set up a toy CVS repository and populate it with a project
mkdir /tmp/toycvs
cvs -d /tmp/toycvs init
mkdir /tmp/toycvs/foo
* Check out the project and check in a new file "bar"
cd /tmp
cvs -d /tmp/toycvs co foo
cd foo
emacs -nw bar
C-x v v # initiate CVS add
C-c C-c # submit for addition -- you should get CVS@@ on the mode line
C-x v v # initiate initial check-in
C-c C-c # submit for check-in -- mode line should now have CVS-1.1
* Play around with other files and verify that they get checked in at 1.1
* Now modify the bar file and check in at 2.x
C-u C-x v v # initiate check in at named version level
2 # enter version level 2
C-c C-c # submit for check in -- you should now see CVS-2.1
* Add new files and find that they too get checked in at initial version 2.1
I'm not altogether sure that what I see is positively an error, but
this behavior has been quite baffling and I could find no mention of
it in the manuals. Even if it makes sense in some contexts, it would
be nice to be able to specify that I like a different behavior -- that
version numbers of files in the same project should not influence each
other.
The behavior also appears to be incompatible with what CVS itself
does, and on those grounds alone could be regarded as buggy, even if
somebody quite consciously designed vc.el to do this.
Feel free to route this upstream if you like; I imagine that would be
the sane thing to do in this case.
Sorry for submitting this against emacs20, I have had no opportunity
to move to Emacs v21 yet.
/* era */
-- System Information
Debian Release: 2.2
Kernel Version: Linux there 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
Versions of the packages emacs20 depends on:
ii emacsen-common 1.4.12 Common facilities for all emacsen.
ii libc6 2.1.3-20 GNU C Library: Shared libraries and Timezone
ii liblockfile1 1.01 Shared library with NFS-safe locking functio
ii libncurses5 5.0-6.0potato2 Shared libraries for terminal handling
ii xlib6g 3.3.6-11potato shared libraries required by X clients
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found
2008-12-30 7:53 ` bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found Sven Joachim
@ 2008-12-30 10:16 ` Dan Nicolaescu
2008-12-30 10:55 ` bug#1740: marked as done ([era eriksson] vc.el adds new files at v2.1 if other v2.x file found) Emacs bug Tracking System
1 sibling, 0 replies; 3+ messages in thread
From: Dan Nicolaescu @ 2008-12-30 10:16 UTC (permalink / raw)
To: Sven Joachim; +Cc: 1740
Sven Joachim <svenjoac@gmx.de> writes:
> I'm revising old bugs reported against Emacs in Debian and will forward
> some of them here that are still reproducible in current Emacs CVS.
> This one is an example of a very well written bug report.
>
> From: era eriksson <era@iki.fi>
> Subject: Bug#149196: emacs20: vc.el adds new files at v2.1 if other v2.x file found
> To: submit@bugs.debian.org
> Date: Thu, 06 Jun 2002 14:20:13 +0300
> Reply-To: era eriksson <era@iki.fi>, 149196@bugs.debian.org
> Resent-From: era eriksson <era@iki.fi>
>
> Package: emacs20
> Version: 20.7-2
> Severity: normal
>
> It seems that the version control mode vc.el has a "feature" with CVS
> which causes it to check in new files beginning at version number 2.1
> if there is another file whose version number is 2.x in the same
> directory (i.e. CVS module / project).
>
> I had been noticing this more and more frequently over time, but
> hadn't been able to diagnose it correctly. Now here are the steps to
> repro this.
>
>
> * Set up a toy CVS repository and populate it with a project
>
> mkdir /tmp/toycvs
> cvs -d /tmp/toycvs init
> mkdir /tmp/toycvs/foo
>
> * Check out the project and check in a new file "bar"
>
> cd /tmp
> cvs -d /tmp/toycvs co foo
> cd foo
> emacs -nw bar
> C-x v v # initiate CVS add
> C-c C-c # submit for addition -- you should get CVS@@ on the mode line
> C-x v v # initiate initial check-in
> C-c C-c # submit for check-in -- mode line should now have CVS-1.1
>
> * Play around with other files and verify that they get checked in at 1.1
>
> * Now modify the bar file and check in at 2.x
>
> C-u C-x v v # initiate check in at named version level
> 2 # enter version level 2
> C-c C-c # submit for check in -- you should now see CVS-2.1
>
> * Add new files and find that they too get checked in at initial version 2.1
This does not seem to have anything to do with vc.el, after this step if
you do:
$ echo blah > blah
$ cvs add blah
$ cvs ci -m "add blah" blah
RCS file: /tmp/toycvs/foo/blah,v
done
Checking in blah;
/tmp/toycvs/foo/blah,v <-- blah
initial revision: 2.1
done
so CVS adds the new file as version 2.1
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#1740: marked as done ([era eriksson] vc.el adds new files at v2.1 if other v2.x file found)
2008-12-30 7:53 ` bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found Sven Joachim
2008-12-30 10:16 ` Dan Nicolaescu
@ 2008-12-30 10:55 ` Emacs bug Tracking System
1 sibling, 0 replies; 3+ messages in thread
From: Emacs bug Tracking System @ 2008-12-30 10:55 UTC (permalink / raw)
To: Sven Joachim
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Your message dated Tue, 30 Dec 2008 11:48:29 +0100
with message-id <878wpy3pmq.fsf@turtle.gmx.de>
and subject line Re: bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found
has caused the Emacs bug report #1740,
regarding [era eriksson] vc.el adds new files at v2.1 if other v2.x file found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)
--
1740: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1740
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
[-- Attachment #2: Type: message/rfc822, Size: 6108 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 199 bytes --]
I'm revising old bugs reported against Emacs in Debian and will forward
some of them here that are still reproducible in current Emacs CVS.
This one is an example of a very well written bug report.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 3587 bytes --]
From: era eriksson <era@iki.fi>
To: submit@bugs.debian.org
Subject: Bug#149196: emacs20: vc.el adds new files at v2.1 if other v2.x file found
Date: Thu, 06 Jun 2002 14:20:13 +0300
Message-ID: <E17FvJN-00031e-00@there>
Package: emacs20
Version: 20.7-2
Severity: normal
It seems that the version control mode vc.el has a "feature" with CVS
which causes it to check in new files beginning at version number 2.1
if there is another file whose version number is 2.x in the same
directory (i.e. CVS module / project).
I had been noticing this more and more frequently over time, but
hadn't been able to diagnose it correctly. Now here are the steps to
repro this.
* Set up a toy CVS repository and populate it with a project
mkdir /tmp/toycvs
cvs -d /tmp/toycvs init
mkdir /tmp/toycvs/foo
* Check out the project and check in a new file "bar"
cd /tmp
cvs -d /tmp/toycvs co foo
cd foo
emacs -nw bar
C-x v v # initiate CVS add
C-c C-c # submit for addition -- you should get CVS@@ on the mode line
C-x v v # initiate initial check-in
C-c C-c # submit for check-in -- mode line should now have CVS-1.1
* Play around with other files and verify that they get checked in at 1.1
* Now modify the bar file and check in at 2.x
C-u C-x v v # initiate check in at named version level
2 # enter version level 2
C-c C-c # submit for check in -- you should now see CVS-2.1
* Add new files and find that they too get checked in at initial version 2.1
I'm not altogether sure that what I see is positively an error, but
this behavior has been quite baffling and I could find no mention of
it in the manuals. Even if it makes sense in some contexts, it would
be nice to be able to specify that I like a different behavior -- that
version numbers of files in the same project should not influence each
other.
The behavior also appears to be incompatible with what CVS itself
does, and on those grounds alone could be regarded as buggy, even if
somebody quite consciously designed vc.el to do this.
Feel free to route this upstream if you like; I imagine that would be
the sane thing to do in this case.
Sorry for submitting this against emacs20, I have had no opportunity
to move to Emacs v21 yet.
/* era */
-- System Information
Debian Release: 2.2
Kernel Version: Linux there 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
Versions of the packages emacs20 depends on:
ii emacsen-common 1.4.12 Common facilities for all emacsen.
ii libc6 2.1.3-20 GNU C Library: Shared libraries and Timezone
ii liblockfile1 1.01 Shared library with NFS-safe locking functio
ii libncurses5 5.0-6.0potato2 Shared libraries for terminal handling
ii xlib6g 3.3.6-11potato shared libraries required by X clients
[-- Attachment #3: Type: message/rfc822, Size: 2253 bytes --]
From: Sven Joachim <svenjoac@gmx.de>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 1740-done@emacsbugs.donarmstrong.com
Subject: Re: bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found
Date: Tue, 30 Dec 2008 11:48:29 +0100
Message-ID: <878wpy3pmq.fsf@turtle.gmx.de>
On 2008-12-30 11:16 +0100, Dan Nicolaescu wrote:
> This does not seem to have anything to do with vc.el, after this step if
> you do:
>
> $ echo blah > blah
> $ cvs add blah
> $ cvs ci -m "add blah" blah
> RCS file: /tmp/toycvs/foo/blah,v
> done
> Checking in blah;
> /tmp/toycvs/foo/blah,v <-- blah
> initial revision: 2.1
> done
>
> so CVS adds the new file as version 2.1
Yes, I can confirm this. So I'll probably reassign the Debian bug to
the cvs package.
Thanks and sorry for the noise,
Sven
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-12-30 10:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <878wpy3pmq.fsf@turtle.gmx.de>
2008-12-30 7:53 ` bug#1740: [era eriksson] vc.el adds new files at v2.1 if other v2.x file found Sven Joachim
2008-12-30 10:16 ` Dan Nicolaescu
2008-12-30 10:55 ` bug#1740: marked as done ([era eriksson] vc.el adds new files at v2.1 if other v2.x file found) Emacs bug Tracking System
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).