[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RE: dump friendly repository management question

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-13 20:30:56 CET

First, I apologize to the list for sending the original in non-ASCII.
Now any of us using Outlook pretty much have to top-post.
Ron, I am looking for opinions from people like you on alternative means
to control clutter while still permitting successful full history dump
filters. I knew the history would be preserved within the initial
repository. It is future migration to other repositories that concerns


        From: Ron Romero [mailto:Ron.Romero@troux.com]
        Sent: Tuesday, November 13, 2007 11:36 AM
        To: users@subversion.tigris.org
        Subject: RE: dump friendly repository management question
        If "Archived" is a folder within the Subversion repository, then
moving it to Archived *would* keep history. We've used a similar
philosophy with our dead projects. It does reduce visual clutter, but
it's still all there when we need it.
        OTOH, if you're thinking about moving it *out* of the Subversion
repository, the way you would with cvs, then I'd advise you to rethink.
        Ron Romero
        Troux Technologies
        cell: 512-809-1162
        IM: RonZRomero

        Nothing is wholly good or wholly bad - except Twinkies.


        From: Bicking, David (HHoldings, IT)
        Sent: Tuesday, 13 November 2007 8:17 AM
        To: users@subversion.tigris.org
        Subject: dump friendly repository management question
        I am contemplating a repository layout which uses the "all
projects in one repository" pattern. I want to be able to dump
individual projects, with all the history, and load them into different
repositories in the future. Given the nature of svndumpfilter{1..3}, I
am concerned about copy/move operations.
        As time passes, projects become inactive for one reason or
another. These projects would be "archived". One proposal is to move
those projects into a folder called "Archived". However, as soon as
this is done, we will lose the ability to extract those projects, with
history, from the repository. I want to avoid this problem. However, I
don't want visual clutter in the repository. We want to quickly
differentiate between active and archived projects visually.
        I am also unsure about the consequences of moving a project to
Archived, and later moving it back to its original location.
        Do any of you have experience in this area you can share with
me? What works best for you?
        I have one idea at the moment: create an "archived" user and
once a project is archived, make it readable only by user "archived" and
group "Admin".
        David Bicking
        Heritage Holdings IT
        55 Farmington Ave., Suite 605
        This communication, including attachments, is
        for the exclusive use of addressee and may contain proprietary,
        confidential and/or privileged information. If you are not the
        recipient, any use, copying, disclosure, dissemination or
distribution is
        strictly prohibited. If you are not the intended recipient,
please notify
        the sender immediately by return e-mail, delete this
communication and
        destroy all copies.

        This message may contain confidential information. If you have
received this e-mail in error, do not use, copy or distribute it. Do not
open any attachments. Delete it immediately from your system and notify
the sender promptly by e-mail that you have done so. Thank you.
Received on Tue Nov 13 20:32:05 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.