[Top][All Lists]

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

Undeliverable Message

Subject: Undeliverable Message
Date: Sat, 16 Jun 2001 20:32:35 +0100

To:            address@hidden@Servers["CVS-II Discussion Mailing List" 

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.

        VNM3043:  Andre address@hidden address@hidden


   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is
   10,000.  The default message limit is 1000 messages.
   Administrators can set message limits using the
   Mailbox  Settings function available in the
   Manage User menu  (MUSER).

   When a user's mailbox reaches the limit, the
   user must delete some of the messages before
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------

[ On Saturday, June 16, 2001 at 09:50:38 (-0700), Paul Sander wrote: ]
> One of CVS' worst design flaws is that it does NOT version directories.

That's *NOT* a flaw!  That's a *FEATURE*!  And a very valuable one at that!

In fact one can easily argue that it was an explicit design goal!

The only major implementation flaw with this feature in CVS is that when
a previously deleted file is re-added then the new file appears to have
the history of the old deleted file too.  There are several possible
ways to fix this, the easiest being to simply have "cvs log" and friends
stop printing history, by default, just after they encounter a "dead"

> Files appear as they are added,

and disappear as they are removed...

>  and CVS relies on timestamps and tags
> to reproduce the proper combination of file versions from the past.

timestamps _OR_ tags, but hopefully people primarily use tags for
anything related to release management.

Yes, it's all quite nifty and automatic, just as it should be.

> The result is that managing empty directories is difficult at best, and

Why would you ever want to manage empty directories?!?!?!?!?

You should create them in your build process, if absolutely necessary
(eg. "make obj" in the *BSD build process).

This stupid issue has been discussed to death over the past eight or so
years.  Why you want to always bring it up again is a mystery to me.

> you can't reorganize your sources (e.g. rename a file).

Yes, you CAN.  All rename operations, in all facets of computing, is
simply a deletion and an addition in whatever order is appropriate (and
sometimes it's an atomic operation from the point of view of the user,
and sometimes, as currently in CVS, it's not).

CVS even optimises away the handling of deleted files so that moving
files from one directory to another doesn't always cause the performance
penalty of scanning all the deleted files.

Quit spreading F.U.D. Paul.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

Info-cvs mailing list

This Mail has been checked for Viruses
Attention: Encrypted Mails can NOT be checked !


Diese Mail wurde auf Viren ueberprueft
Hinweis: Verschluesselte Mails koennen NICHT geprueft werden!

reply via email to

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