From users-return-11843-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Sun Oct 23 20:00:18 2011 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BF1B9348 for ; Sun, 23 Oct 2011 20:00:18 +0000 (UTC) Received: (qmail 49970 invoked by uid 500); 23 Oct 2011 20:00:17 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 49939 invoked by uid 500); 23 Oct 2011 20:00:17 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 49931 invoked by uid 99); 23 Oct 2011 20:00:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 20:00:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ludovic.lambert@gmail.com designates 209.85.210.171 as permitted sender) Received: from [209.85.210.171] (HELO mail-iy0-f171.google.com) (209.85.210.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 20:00:13 +0000 Received: by iaen33 with SMTP id n33so11064146iae.16 for ; Sun, 23 Oct 2011 12:59:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0kWzPQPmNRPtfM7mpef2p8mByipriaS3S/8I5RXwmfI=; b=vS1uPLKUAhzDNb1AXTr6cJyh2/cJ0e3LiZg4w5a3VOjGefhFPMpxsBJggI6UsDQFRm 1heMGCCDcZr3sMdsgytGw1H9lNbvBzdtVDD652yP2b2NbSjMBN3UulP91DZGiqkPUjg5 g6a7uwDNIWf7llp8UQKINpp/77XUlSO6VpnOA= MIME-Version: 1.0 Received: by 10.68.44.168 with SMTP id f8mr38922285pbm.11.1319399992025; Sun, 23 Oct 2011 12:59:52 -0700 (PDT) Received: by 10.142.172.16 with HTTP; Sun, 23 Oct 2011 12:59:51 -0700 (PDT) In-Reply-To: References: Date: Sun, 23 Oct 2011 21:59:51 +0200 Message-ID: Subject: Re: info subversion From: Ludovic Lambert To: filomena ciola Cc: users@subversion.apache.org Content-Type: multipart/alternative; boundary=bcaec520f0cdd763e204affcbff0 --bcaec520f0cdd763e204affcbff0 Content-Type: text/plain; charset=UTF-8 Hi Filomena, Restricting access on a revision basis is not possible. You can remove old versions or part of your repo by using the dumpfilter command. 1. Dump your current repo 2. Use dumpfilter to filter unwanted elements 3. Reload filtered dump into a new repo. Doc: http://svnbook.red-bean.com/en/1.7/svn.ref.svndumpfilter.html Exemple 1 - Removing old revisions: http://robmayhew.com/delete-parts-of-subversion-history/ Exemple 2 - Removing a directory: http://www.lesnikowski.com/blog/index.php/how-to-permanently-remove-svn-folder/ Cheers, Ludovic 2011/10/23 Nico Kadel-Garcia > On Mon, Oct 10, 2011 at 12:28 PM, filomena ciola > wrote: > > Hello, > > Please I need your help for a little question: > > I need to erase all the old revisions, if it' s possible, how can I do > for > > make this automatically? if this isn't possible, can I put a pw so only > > authorized personell can see old revision? > > Thank you for your interesting > > With best regards > > > > > > Mimma Ciola > > If they can see the file, in Subversion, they can see all the old > relevant revisions from that repository. They may not be able to see > *other* files if you have access to them blocked in Apache or svnserve > managed access. > > It's also vaguely feasible that if you used svn+ssh based access, the > relevant "svn" user could be made not a member of the appropriate > groups to see that old revision at all. But this would get *nasty*, > very quickly, It would be like replacing the command "rm" with > something that moves files aside. It would work until it broke, > *badly*. > --bcaec520f0cdd763e204affcbff0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Filomena,

Restricting access on a revision basis is not possible.=
You can remove old versions or part of your repo by using the dumpfilt= er command.
1. Dump your current repo
2. Use dumpfilter to filter unw= anted elements
3. Reload filtered dump into a new repo.
Doc: http://svnbook.red-bean.com= /en/1.7/svn.ref.svndumpfilter.html
Exemple 1 - Removing old revision= s: htt= p://robmayhew.com/delete-parts-of-subversion-history/
Exemple 2 - Removing a directory: http://www.lesnikowski.c= om/blog/index.php/how-to-permanently-remove-svn-folder/

Cheers,<= br> Ludovic

2011/10/23 Nico Kadel-Garcia <nkadel@gmail.com&= gt;
On Mon, Oct 10, 2011 at 12:28 PM, filomen= a ciola
<ciolafilomena@gmail.com&= gt; wrote:
> Hello,
> Please I need your help for a little question:
> I need to erase all the old revisions, if it' s possible, how can = I do for
> make this automatically? if this isn't possible, can I put a pw so= only
> authorized personell can see old revision?
> Thank you for your interesting
> With best regards
>
>
> Mimma Ciola

If they can see the file, in Subversion, they can see all the o= ld
relevant revisions from that repository. They may not be able to see
*other* files if you have access to them blocked in Apache or svnserve
managed access.

It's also vaguely feasible that if you used svn+ssh based access, the relevant "svn" user could be made not a member of the appropriate=
groups to see that old revision at all. =C2=A0But this would get *nasty*, very quickly, It would be like replacing the command "rm" with something that moves files aside. It would work until it broke,
*badly*.

--bcaec520f0cdd763e204affcbff0--