[Top][All Lists]

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

Re: import inconsistency

From: Pierre Asselin
Subject: Re: import inconsistency
Date: Fri, 13 Jun 2003 20:20:57 -0400
User-agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.2.19-7.0.1 (i586))

Paul Edwards <kerravon@nosppaam.w3.to> wrote:
> "Stefan Monnier" <monnier+gnu.cvs.bug/news/@flint.cs.yale.edu> wrote in 
> message 5l65naffjy.fsf@rum.cs.yale.edu">news:5l65naffjy.fsf@rum.cs.yale.edu...
>> Files in the Attic is a very common place situation: every time someone adds
>> a file to a branch before it's added to the trunk,

> Very rare for a home user to do something like that.  You need
> a big project to see something like that happening.

This is from my home-user repository:

    Script started on Fri Jun 13 19:57:56 2003

    sh-2.04$ find /home/pa/cvsroot -name Attic | xargs ls

    check_order.sh,v    delta_slider.o,v  flvmesh.h,v  stripmesh.pl,v
    delta_adjuster.o,v  flvmesh.cc,v      jrs.c,v

And I'm not even trying.  My other home-user repository, which is
maybe 4 years old, has 155 Attics scattered all over the place.
They're quite common.

> Once a file is removed, normally no-one cares about it.  It's
> dead and forgotten.  In my case it is precious and remembered.

No, files get created on branches all the time and need to be merged
later.  Dead files get resurrected all the time, too.

> BTW, if these things were common, how come I was the first
> to complain about cvs rdiff -s, first to complain about cvs diff
> with two tags, first to complain about cvs diff not understanding
> that dead means dead and no means no, first to complain that
> branches interfere with normal import processing...  maybe the
> underlying explanation is that I'm just a natural-born whinger
> with too much time on his hands?  :-)

You break any software you touch, that's what it is :-)

Actually, the one thing you do that is very unusual is that you don't
use a trunk.  The entire import functionality assume that there is, or
going to be one.

reply via email to

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