Re: import inconsistency

[Paul Edwards]

"Mark D. Baushke" <mdb@cvshome.org> wrote in message 
news:mailman.7914.1055649672.21513.bug-cvs@gnu.org...
> Paul Edwards <kerravon@nosppaam.w3.to> writes:
>
> > "Stefan Monnier" <monnier+gnu.cvs.bug/news/@flint.cs.yale.edu> wrote in 
> > message 5lr85webh1.fsf@rum.cs.yale.edu">news:5lr85webh1.fsf@rum.cs.yale.edu...
> > > >>>>> "Larry" == Larry Jones <lawrence.jones@eds.com> writes:
> > > > all branches would be very, very wrong.  If I have a branch for
> > > > experimental code, I certainly don't want files added to it to suddenly
> > > > start showing up on the trunk, too.
> > >
> > > Indeed.  It's bad enough that the directories show up on the trunk.
> >
> > Show up on the trunk during which operation?
>
> My guess would be doing a 'cvs checkout' ... doing a checkout on the
> trunk differs from doing it on a branch in that the -P switch is already
> implied on the branch, you need to b explicit when you are using the
> trunk.

Ok, you can probably tell that I don't do checkouts on the head
very often.  :-)

> I believe that the UI is intended to allow you to resurrect files from
> an otherwise empty (all files 'dead' and in the Attic) directory in the
> repository...

Ok.  Like most weird computer things, there is usually a complex
reason why it actually makes perfect sense.  :-)

BFN.  Paul.