Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 99FDF200BBD for ; Tue, 8 Nov 2016 14:32:33 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 98A15160B0A; Tue, 8 Nov 2016 13:32:33 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B9EE5160AFA for ; Tue, 8 Nov 2016 14:32:32 +0100 (CET) Received: (qmail 57970 invoked by uid 500); 8 Nov 2016 13:32:31 -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 57951 invoked by uid 99); 8 Nov 2016 13:32:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2016 13:32:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 170C91A0257 for ; Tue, 8 Nov 2016 13:32:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.63 X-Spam-Level: ** X-Spam-Status: No, score=2.63 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YIlRlJp2ZOxs for ; Tue, 8 Nov 2016 13:32:29 +0000 (UTC) Received: from mail-it0-f48.google.com (mail-it0-f48.google.com [209.85.214.48]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9F3CE5F23C for ; Tue, 8 Nov 2016 13:32:27 +0000 (UTC) Received: by mail-it0-f48.google.com with SMTP id q124so206033769itd.1 for ; Tue, 08 Nov 2016 05:32:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=j3AbAWeOaGhkWLxAyLR9hDqfpWz4tULA/CaeVEstKE0=; b=Uf3U2lRswQUt4/lBRmeL9P9CAyKrf02qlu9oJLYvjkjAoLg0gsOsjmBzPAcWI0BcwC q/zN+Cu4OkAfMfPx2NuOwgIL6oVdSTeP1yLbGLdtf7Ib48R1eGGy0GMKPNFByWFIMrcJ FHRJe5OgYdZENHwxQZk/YToCqGgasAIrPbDMU4r0A4i1I6YmTOLfRyBBsJPQumDfBN1J QjUC+iPMC8T4YnE315J5MJqsncpc+rrLXNb13BDDJ5dtA/UBdosFjT4Ls9Y3/RIE5rjp rd3XB/TWRz6KtaZ4BeVaOCDV7XrumdgI+/XDuA2TTrsTNqKWh+5NdQoya0/1ygpoMkwA siBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=j3AbAWeOaGhkWLxAyLR9hDqfpWz4tULA/CaeVEstKE0=; b=RblWAqmOLCIh4PE/LZTcgMLlAYHblyYPrh93FkWzLijCXHJoYcsotqvGYgU7mIn7dy 9BWqtH+nAp21dE3HAropqIg6OOtGBKBsWr1JDH9UK4FYY6mR678+jR2XCkBGDBtds80t rk6v3rt7adXDFJSflpjUaMwJiR5sLSTC8AZG8De8M828YoFHDdHhFdU7aFSc3Pp9dRFv CInr99im7lpJ5hR4N52I7kG6/cz0i6FvDmUJbwFskBocNkNvtktSYoNYW17uhbQy8ilQ H/W3UumgRy4klmVYIFDlUgKO04OSF8Sxhe89lc/NfoZHdOi1ZCvlP/QLAVhyf4CQ3Bn8 MY5g== X-Gm-Message-State: ABUngvcQLZw5iPukpgWQy0yloXGbzILuKbCwOif+US635ooVMeee8MZXgYzrjnybCZ/EgpLWIyI3TtZXZlPADw== X-Received: by 10.107.167.1 with SMTP id q1mr14936047ioe.110.1478611876029; Tue, 08 Nov 2016 05:31:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.123.217 with HTTP; Tue, 8 Nov 2016 05:31:15 -0800 (PST) In-Reply-To: References: <7f4a7711-5b18-f19b-b822-15e56f64a99f@tibco.com> From: gyanendra ojha Date: Tue, 8 Nov 2016 19:01:15 +0530 Message-ID: Subject: Re: Svn branching issue To: "Cooke, Mark" Cc: "users@subversion.apache.org" Content-Type: multipart/alternative; boundary=001a1141caeca1ab130540ca279a archived-at: Tue, 08 Nov 2016 13:32:33 -0000 --001a1141caeca1ab130540ca279a Content-Type: text/plain; charset=UTF-8 ahh i saw that even after source branch gets deleted i am able to access the path in history of target branch thanks guys for your help :) On Tue, Nov 8, 2016 at 4:54 PM, Cooke, Mark wrote: > > -----Original Message----- > > From: gyanendra ojha [mailto:ojhagyanendra3@gmail.com] > > Sent: 08 November 2016 11:01 > > > > Hi Cooke, > > > > i think this is a limitation in svn that should be fixed. > > Sorry but I think most people here will disagree with that. > > > without this in place, we would never be able to achieve moving branches > to > > different location as history will still point to old path that can't be > > accessed as it has been deleted > > Why do you think it cannot be accessed, what have you tried? > > You do not seem to understand what subversion is and how it works. The > path can *never* be deleted and will *always* remain accessible at the old > path (if you format the URL with a revision). Other people have suggested > you read up on "peg" and "operative" revisions and have tried to explain > that "delete" only removes the path from the "current" view. That is why > the old paths show up in the history and why you can still see them. > > The subversion book is online and comprehensive, I suggest you read > through some of that, including "Peg and Operative revisions": > http://svnbook.red-bean.com/en/1.8/svn.advanced.pegrevs.html > > > In my project , the folders and branches have been created in very > improper > > way and now there has been critical need to reorganise the messy branch > > structure in svn by moving and recreating proper streamlined branch > structure > > If there is real mess you could consider "parking" the repository (keeping > it to access the history if required) and creating a new repository with > the required structure. How does that sound? > > > now, you are saying history will still point to old location, but now > that > > old location has been deleted as i had to cleanup old unwanted branches > and > > folders, i won't be able to access the path showing in svn log and > therefore > > those logs or history are not relevant for me > > As above, you cannot stop access to those old paths, you just need to know > how to access them (using the revision syntax in the URL) or using your > GUI's log browser etc. (note that the core subversion project does not > include a GUI so it helps if you mention what GUI you are using and what > platform you are on). > > > and my quest for reorganising svn branch structure in my project will be > > failed > > No, you can always reorganise the structure (and still access all the > history). > > > don't you guys think, it is a serious limitation which need to be > overcome ? > > No, the limitation you see is not actually there. > > I still do not understand if you have an actual problem with something you > have tried to do. Hopefully this (and Stefan's post) will help you. > > ~ mark c > > --001a1141caeca1ab130540ca279a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
= ahh i saw that even after source branch gets deleted=C2=A0

i am able to access the path in hi= story of target branch


tha= nks guys for your help :)


On Tue, Nov 8, 2016 at 4:54 PM, Cooke, Mark = <mark.cooke@= siemens.com> wrote:
> -----Original Message-----
> From: gyanendra ojha [mailto:ojhagyanendra3@gmail.com]
> Sent: 08 November 2016 11:01
>
> Hi Cooke,
>
> i think this is a limitation in svn that should be fixed.

Sorry but I think most people here will disagree with that.

> without this in place, we would never be able to achieve moving branch= es to
> different location as history will still point to old path that can= 9;t be
> accessed as it has been deleted

Why do you think it cannot be accessed, what have you tried?

You do not seem to understand what subversion is and how it works.=C2=A0 Th= e path can *never* be deleted and will *always* remain accessible at the ol= d path (if you format the URL with a revision).=C2=A0 Other people have sug= gested you read up on "peg" and "operative" revisions a= nd have tried to explain that "delete" only removes the path from= the "current" view.=C2=A0 That is why the old paths show up in t= he history and why you can still see them.

The subversion book is online and comprehensive, I suggest you read through= some of that, including "Peg and Operative revisions":
http://svnbook.red-bean.com/en/1.8/= svn.advanced.pegrevs.html

> In my project , the folders and branches have been created in very imp= roper
> way and now there has been critical need to reorganise the messy branc= h
> structure in svn by moving and recreating proper streamlined branch st= ructure

If there is real mess you could consider "parking" the rep= ository (keeping it to access the history if required) and creating a new r= epository with the required structure.=C2=A0 How does that sound?

> now, you are saying history will still point to old location, but now = that
> old location has been deleted as i had to cleanup old unwanted branche= s and
> folders, i won't be able to access the path showing in svn log and= therefore
> those logs or history are not relevant for me

As above, you cannot stop access to those old paths, you just need t= o know how to access them (using the revision syntax in the URL) or using y= our GUI's log browser etc. (note that the core subversion project does = not include a GUI so it helps if you mention what GUI you are using and wha= t platform you are on).

> and my quest for reorganising svn branch structure in my project will = be
> failed

No, you can always reorganise the structure (and still access all th= e history).

> don't you guys think, it is a serious limitation which need to be = overcome ?

No, the limitation you see is not actually there.

I still do not understand if you have an actual problem with something you = have tried to do.=C2=A0 Hopefully this (and Stefan's post) will help yo= u.

~ mark c


--001a1141caeca1ab130540ca279a--