Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 45092 invoked from network); 13 Jun 2005 11:52:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jun 2005 11:52:59 -0000 Received: (qmail 65671 invoked by uid 500); 13 Jun 2005 11:52:57 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 65632 invoked by uid 99); 13 Jun 2005 11:52:57 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of gazarenkov@gmail.com designates 64.233.162.192 as permitted sender) Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.192) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 13 Jun 2005 04:52:55 -0700 Received: by zproxy.gmail.com with SMTP id 9so270244nzo for ; Mon, 13 Jun 2005 04:52:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:from; b=fIcjLgZd9Y5yWzCFVffw+NwYK+RhnsZmyfZiicQx9pI68ooxYFqSqGakVhFn0yh51COdyhMwhpR4QHxpRHLhcSLvyslNPl4WaWx7js21U6C98q7IrePpa7BkrIVvrhkJHw2HnxEtYJzCPh9ztvi5aoqfxaaLZ7UjMwoq18O/dtc= Received: by 10.36.39.19 with SMTP id m19mr2591321nzm; Mon, 13 Jun 2005 04:52:45 -0700 (PDT) Received: from Gennady ([82.207.77.45]) by mx.gmail.com with ESMTP id 6sm2954031nzn.2005.06.13.04.52.42; Mon, 13 Jun 2005 04:52:45 -0700 (PDT) Message-ID: <021401c5700e$6bb1bab0$f273020a@Gennady> To: , References: <42A9B4D4.1050806@anyware-tech.com> <42AAFEC4.4080508@anyware-tech.com> <8be731880506121151400825fe@mail.gmail.com> <020501c56fed$f4781590$f273020a@Gennady> Subject: Re: Getting VersionHistory after removing of a Node Date: Mon, 13 Jun 2005 14:52:42 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 From: Gennady Azarenkov X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N hi david, yes, i get it, that was rather mine misunderstanding :) thank you, gena ----- Original Message ----- From: "David Nuescheler" To: Cc: Sent: Monday, June 13, 2005 1:53 PM Subject: Re: Getting VersionHistory after removing of a Node hi gennady, > IMHO it is good behaviour if there is only one versionable node belonging > to > that VH > but i am not sure if it is correct to remove all versionable nodes (in all > workspaces) > belonging to that VH (especially if versionable nodes from different > workspaces > have base versions belong to different branches)? > i think we can not to change version history until there are at least one > node connected to it > and remove the version history along with the last versionable connected > to > it as you suggest. the way i read tobi's suggestion it was not to remove any versionable node whatsoever. i think it was that based on the fact that the versionhistory is empty and has no reference (eg. versionable node) pointing to that particular vh, to "garbage collect" that version history. or am i misreading something? regards, david