You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by gyanendra ojha <oj...@gmail.com> on 2016/11/07 06:26:09 UTC
Svn branching issue
Hi,
I was assigned a task to move a branch or folder to different location in
svn
Making sure that history of the old branch is retained and not lost
I was able to do it and history was showing in even new branch
But my problem is that when i do svn log in new branch location..it shows
me path still of old branch
I want history for this new branch to change as per new branch path..so
that even in case the old branch gets deleted..i might be able to view the
changes showing in svn log by going to the path
Please help me out if it is possible
Re: Svn branching issue
Posted by Stefan Sperling <st...@elego.de>.
On Mon, Nov 07, 2016 at 11:40:27PM +0530, gyanendra ojha wrote:
> Ok so u mean ..there is no way out for this..no solution
Yes, Subversion simply does not work in the way you expect.
Subversion was deliberately designed in a way that makes renaming
old things in history impossible. You can only move forward in
history and build upon what you already have. Like in real life,
in Subversion you cannot undo what happened in the past (as in,
you cannot undo what happened in past revisions of the repository).
Well, with some exceptions. But I don't think these apply here:
http://subversion.apache.org/faq.html#removal
Re: Svn branching issue
Posted by Stefan Hett <st...@egosoft.com>.
Hi,
On 11/8/2016 12:00 PM, gyanendra ojha wrote:
> Hi Cooke,
>
> i think this is a limitation in svn that should be fixed.
>
> 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
I'm wondering whether you are using here wrong assumptions. Certainly no
history is removed/deleted, if you rename/move a file/directory. The
history is still present.
To explain the situation:
Assume you have a record of the financial record of Marry Jane Mayer.
Now she get's married at date x and changes her last name to Nickson.
If you query the history of Marry Jane Meyer for the time <=x you will
get the record of Marry Jane Nickson. Aka: History/Data is always to be
seen in relation to a time/date (the revision). Nothing is removed, but
if you want to query the data for a file which is called foo at the
current time but was renamed at time x from bar, then if you want to
query foo's data at time <=x you have to state that the file you request
the data for was named bar back then (not foo, which might also have
existed at the same time, but would have been a completely different file).
>
> 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
>
> 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
If you query the whole history of file foo, then this will contain the
history also before the file was renamed.
>
> [...]
>
>
>
P.S. please don't top post
--
Regards,
Stefan Hett
Re: Svn branching issue
Posted by Branko Čibej <br...@apache.org>.
On 30.12.2016 06:04, gyanendra ojha wrote:
> Hi Ryan,
>
> Thanks for reply, after checking out fresh copy of Target Support Files
> when i try to do svn commit to path
> *http://192.168.1.153/jetrepo/jetsvn/Application/CAPTIVE_SOCIAL/MSGCONNECT/Code/IOS/Trunk/MSGConnect/Pods/Target
> <http://192.168.1.153/jetrepo/jetsvn/Application/CAPTIVE_SOCIAL/MSGCONNECT/Code/IOS/Trunk/MSGConnect/Pods/Target>
> Support Files*
>
> as you can see there is space in "Target Support Files" which is reported
> as not found during commit by SVN as below
It is not reported as not found, it is reported as out of date, and the
message clearly states that you have to 'svn update' first.
-- Brane
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
Hi Ryan,
Thanks for reply, after checking out fresh copy of Target Support Files
when i try to do svn commit to path
*http://192.168.1.153/jetrepo/jetsvn/Application/CAPTIVE_SOCIAL/MSGCONNECT/Code/IOS/Trunk/MSGConnect/Pods/Target
<http://192.168.1.153/jetrepo/jetsvn/Application/CAPTIVE_SOCIAL/MSGCONNECT/Code/IOS/Trunk/MSGConnect/Pods/Target>
Support Files*
as you can see there is space in "Target Support Files" which is reported
as not found during commit by SVN as below
[image: Inline image 1]
On Thu, Dec 29, 2016 at 10:40 PM, Ryan Schmidt <
subversion-2016@ryandesign.com> wrote:
>
> > On Dec 29, 2016, at 01:51, gyanendra ojha <oj...@gmail.com>
> wrote:
> >
> > Hello guys,
> >
> > I have one more issue
> >
> > I have noticed that when there is space in folder name in svn
> repository..i face issues while adding any file or folder to the folder
> from my local working copy saying that the path does not exist on svn
> >
> > Looks like svn cant read space in naming
> >
> > Please help i cant remove space and i want to continue with that
>
> svn should have no problem dealing with spaces in path names.
>
> Show us the commands you're trying to use, and the error messages you're
> getting back, and maybe we can spot what the problem is.
>
>
>
Re: Svn branching issue
Posted by Ryan Schmidt <su...@ryandesign.com>.
> On Dec 29, 2016, at 01:51, gyanendra ojha <oj...@gmail.com> wrote:
>
> Hello guys,
>
> I have one more issue
>
> I have noticed that when there is space in folder name in svn repository..i face issues while adding any file or folder to the folder from my local working copy saying that the path does not exist on svn
>
> Looks like svn cant read space in naming
>
> Please help i cant remove space and i want to continue with that
svn should have no problem dealing with spaces in path names.
Show us the commands you're trying to use, and the error messages you're getting back, and maybe we can spot what the problem is.
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
Hello guys,
I have one more issue
I have noticed that when there is space in folder name in svn repository..i
face issues while adding any file or folder to the folder from my local
working copy saying that the path does not exist on svn
Looks like svn cant read space in naming
Please help i cant remove space and i want to continue with that
On 8 Nov 2016 19:01, "gyanendra ojha" <oj...@gmail.com> wrote:
> 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 <ma...@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
>> 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
>>
>>
>
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
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 <ma...@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 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
>
>
RE: Svn branching issue
Posted by "Cooke, Mark" <ma...@siemens.com>.
> -----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
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
Hi Cooke,
i think this is a limitation in svn that should be fixed.
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
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
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
and my quest for reorganising svn branch structure in my project will be
failed
don't you guys think, it is a serious limitation which need to be overcome ?
On Tue, Nov 8, 2016 at 1:51 PM, Cooke, Mark <ma...@siemens.com> wrote:
> Is this an XY Problem (http://xyproblem.info/) ?
>
> Can you explain WHY it is important to you to show the new path rather
> than the old? It sounds like you think this is the solution to your
> problem (whatever that is) so you ask about your "solution" rather than the
> problem...
>
> ~ mark c
>
>
> > -----Original Message-----
> > From: gyanendra ojha [mailto:ojhagyanendra3@gmail.com]
> > Sent: 07 November 2016 18:17
> > To: Eric Johnson
> > Cc: users@subversion.apache.org
> > Subject: Re: Svn branching issue
> >
> > See my aim is to create branch a/a.txt from b/a.txt and then del a..and i
> > want history in branch a to show path for branch b not a..is it possible?
> >
> > I know as b is branched from a..modification history of b will habe
> reference
> > of a..but i want other way around
> >
> >
> > On 7 Nov 2016 23:44, "Eric Johnson" <er...@tibco.com> wrote:
> >
> >
> >
> > On 11/7/16 10:10 AM, gyanendra ojha wrote:
> >
> >
> >
> > Ok so u mean ..there is no way out for this..no solution
> >
> >
> >
> > Maybe, maybe not. It isn't clear whether your concern is about
> losing
> > history, or that Subversion doesn't let you rewrite history to reflect
> some
> > arbitrary desired state.
> >
> > Subversion won't lose history.
> >
> > Eric.
> >
> >
> >
> > On 7 Nov 2016 23:37, "Eric Johnson" <eric@tibco.com
> > <ma...@tibco.com>> wrote:
> >
> > On 11/7/16 9:58 AM, gyanendra ojha wrote:
> >
> > hi eric,
> >
> > that is the issue, new branch created from
> old
> > location is
> > having the old path in svn log,i want it to point
> it to
> > newly
> > created branch path
> >
> > for example there is svn old branch
> > //depot/a/a.txt
> >
> > now if i create branch //depot/b from old
> > branch
> >
> > it will have a.txt in b branch..but when i
> go
> > to
> > //depot/b/a.txt and at GUI of SVN..do right click
> and
> > select
> > show log option..it shows history of
> changes
> > done in
> > a.txt but
> > in path section it still shows
> //depot/a/a.txt
> > instead of
> > //depot/b/a.txt..now if old branch gets
> deleted..this
> > history
> > will be irrelevant for me
> >
> >
> > As I said I in my previous response, you should review
> info
> > on peg
> > & operative revisions.
> >
> > Also, even if you delete //depot/a/ , the history of
> > //depot/a
> > persists, it is just not accessible when "peg"
> revision is
> > "HEAD".
> >
> >
> > requirement is to move a/a.txt to new location
> b/a.txt
> > with
> > history retained and that history should have
> changes
> > pointing
> > to new location b/a.txt not a/a.txt
> >
> >
> > With Subversion, you cannot have the history changes
> > pointing to
> > the new location after your move, because that would
> not
> > reflect
> > the actual history! That would be re-writing history
> as if
> > folder
> > "a" never existed.
> >
> > Eric.
> >
> >
> > i hope now u understand my issue
> >
> > On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson
> > <eric@tibco.com
> > <ma...@tibco.com> <mailto:eric@tibco.com
> > <ma...@tibco.com>>> wrote:
> >
> >
> > On 11/6/16 10:26 PM, gyanendra ojha wrote:
> >
> >
> > Hi,
> >
> > I was assigned a task to move a branch or
> > folder to
> > different
> > location in svn
> >
> > Making sure that history of the old branch
> is
> > retained
> > and not
> > lost
> >
> > I was able to do it and history was
> showing in
> > even
> > new branch
> >
> > But my problem is that when i do svn log
> in new
> > branch
> > location..it shows me path still of old
> branch
> >
> >
> > The old location is part of the history of the
> > folder. As new
> > changes appear in the new location, those
> changes
> > will
> > show the
> > new path. Older changes that happened in the
> older
> > location will
> > show the old path.
> >
> > Perhaps you're using something other than the
> > command line
> > client?
> > Perhaps the UI is making this confusing?
> >
> > svn log has a "--stop-on-copy" option that will
> > show you the
> > history of the changes only in the current
> > location.
> >
> > I want history for this new branch to
> change as
> > per
> > new branch
> > path..so that even in case the old branch
> gets
> > deleted..i
> > might be able to view the changes showing
> in
> > svn log
> > by going
> > to the path
> >
> > Subversion will not lose your older changes,
> even
> > if you
> > delete
> > the old path. All that deleting the old path
> does
> > is
> > remove the
> > reference to the contents for current and
> future
> > versions
> > of the
> > parent folder. Older versions of the parent
> folder
> > still
> > contain
> > the older version of the child folder.
> >
> > You might benefit from understanding the
> difference
> > between the
> > "peg" and "operative" versions.
> >
> > http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html>
> > <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html> >
> > <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html>
> > <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> > bean.com/en/1.7/svn.advanced.pegrevs.html> >>
> >
> > Eric.
> >
> >
> >
> >
> >
>
>
RE: Svn branching issue
Posted by "Cooke, Mark" <ma...@siemens.com>.
Is this an XY Problem (http://xyproblem.info/) ?
Can you explain WHY it is important to you to show the new path rather than the old? It sounds like you think this is the solution to your problem (whatever that is) so you ask about your "solution" rather than the problem...
~ mark c
> -----Original Message-----
> From: gyanendra ojha [mailto:ojhagyanendra3@gmail.com]
> Sent: 07 November 2016 18:17
> To: Eric Johnson
> Cc: users@subversion.apache.org
> Subject: Re: Svn branching issue
>
> See my aim is to create branch a/a.txt from b/a.txt and then del a..and i
> want history in branch a to show path for branch b not a..is it possible?
>
> I know as b is branched from a..modification history of b will habe reference
> of a..but i want other way around
>
>
> On 7 Nov 2016 23:44, "Eric Johnson" <er...@tibco.com> wrote:
>
>
>
> On 11/7/16 10:10 AM, gyanendra ojha wrote:
>
>
>
> Ok so u mean ..there is no way out for this..no solution
>
>
>
> Maybe, maybe not. It isn't clear whether your concern is about losing
> history, or that Subversion doesn't let you rewrite history to reflect some
> arbitrary desired state.
>
> Subversion won't lose history.
>
> Eric.
>
>
>
> On 7 Nov 2016 23:37, "Eric Johnson" <eric@tibco.com
> <ma...@tibco.com>> wrote:
>
> On 11/7/16 9:58 AM, gyanendra ojha wrote:
>
> hi eric,
>
> that is the issue, new branch created from old
> location is
> having the old path in svn log,i want it to point it to
> newly
> created branch path
>
> for example there is svn old branch
> //depot/a/a.txt
>
> now if i create branch //depot/b from old
> branch
>
> it will have a.txt in b branch..but when i go
> to
> //depot/b/a.txt and at GUI of SVN..do right click and
> select
> show log option..it shows history of changes
> done in
> a.txt but
> in path section it still shows //depot/a/a.txt
> instead of
> //depot/b/a.txt..now if old branch gets deleted..this
> history
> will be irrelevant for me
>
>
> As I said I in my previous response, you should review info
> on peg
> & operative revisions.
>
> Also, even if you delete //depot/a/ , the history of
> //depot/a
> persists, it is just not accessible when "peg" revision is
> "HEAD".
>
>
> requirement is to move a/a.txt to new location b/a.txt
> with
> history retained and that history should have changes
> pointing
> to new location b/a.txt not a/a.txt
>
>
> With Subversion, you cannot have the history changes
> pointing to
> the new location after your move, because that would not
> reflect
> the actual history! That would be re-writing history as if
> folder
> "a" never existed.
>
> Eric.
>
>
> i hope now u understand my issue
>
> On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson
> <eric@tibco.com
> <ma...@tibco.com> <mailto:eric@tibco.com
> <ma...@tibco.com>>> wrote:
>
>
> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>
>
> Hi,
>
> I was assigned a task to move a branch or
> folder to
> different
> location in svn
>
> Making sure that history of the old branch is
> retained
> and not
> lost
>
> I was able to do it and history was showing in
> even
> new branch
>
> But my problem is that when i do svn log in new
> branch
> location..it shows me path still of old branch
>
>
> The old location is part of the history of the
> folder. As new
> changes appear in the new location, those changes
> will
> show the
> new path. Older changes that happened in the older
> location will
> show the old path.
>
> Perhaps you're using something other than the
> command line
> client?
> Perhaps the UI is making this confusing?
>
> svn log has a "--stop-on-copy" option that will
> show you the
> history of the changes only in the current
> location.
>
> I want history for this new branch to change as
> per
> new branch
> path..so that even in case the old branch gets
> deleted..i
> might be able to view the changes showing in
> svn log
> by going
> to the path
>
> Subversion will not lose your older changes, even
> if you
> delete
> the old path. All that deleting the old path does
> is
> remove the
> reference to the contents for current and future
> versions
> of the
> parent folder. Older versions of the parent folder
> still
> contain
> the older version of the child folder.
>
> You might benefit from understanding the difference
> between the
> "peg" and "operative" versions.
>
> http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html>
> <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html> >
> <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html>
> <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html <http://svnbook.red-
> bean.com/en/1.7/svn.advanced.pegrevs.html> >>
>
> Eric.
>
>
>
>
>
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
See my aim is to create branch a/a.txt from b/a.txt and then del a..and i
want history in branch a to show path for branch b not a..is it possible?
I know as b is branched from a..modification history of b will habe
reference of a..but i want other way around
On 7 Nov 2016 23:44, "Eric Johnson" <er...@tibco.com> wrote:
>
> On 11/7/16 10:10 AM, gyanendra ojha wrote:
>
>>
>> Ok so u mean ..there is no way out for this..no solution
>>
>> Maybe, maybe not. It isn't clear whether your concern is about losing
> history, or that Subversion doesn't let you rewrite history to reflect some
> arbitrary desired state.
>
> Subversion won't lose history.
>
> Eric.
>
>>
>> On 7 Nov 2016 23:37, "Eric Johnson" <eric@tibco.com <mailto:
>> eric@tibco.com>> wrote:
>>
>> On 11/7/16 9:58 AM, gyanendra ojha wrote:
>>
>> hi eric,
>>
>> that is the issue, new branch created from old location is
>> having the old path in svn log,i want it to point it to newly
>> created branch path
>>
>> for example there is svn old branch //depot/a/a.txt
>>
>> now if i create branch //depot/b from old branch
>>
>> it will have a.txt in b branch..but when i go to
>> //depot/b/a.txt and at GUI of SVN..do right click and select
>> show log option..it shows history of changes done in
>> a.txt but
>> in path section it still shows //depot/a/a.txt instead of
>> //depot/b/a.txt..now if old branch gets deleted..this history
>> will be irrelevant for me
>>
>>
>> As I said I in my previous response, you should review info on peg
>> & operative revisions.
>>
>> Also, even if you delete //depot/a/ , the history of //depot/a
>> persists, it is just not accessible when "peg" revision is "HEAD".
>>
>>
>> requirement is to move a/a.txt to new location b/a.txt with
>> history retained and that history should have changes pointing
>> to new location b/a.txt not a/a.txt
>>
>>
>> With Subversion, you cannot have the history changes pointing to
>> the new location after your move, because that would not reflect
>> the actual history! That would be re-writing history as if folder
>> "a" never existed.
>>
>> Eric.
>>
>>
>> i hope now u understand my issue
>>
>> On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson <eric@tibco.com
>> <ma...@tibco.com> <mailto:eric@tibco.com
>> <ma...@tibco.com>>> wrote:
>>
>>
>> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>>
>>
>> Hi,
>>
>> I was assigned a task to move a branch or folder to
>> different
>> location in svn
>>
>> Making sure that history of the old branch is retained
>> and not
>> lost
>>
>> I was able to do it and history was showing in even
>> new branch
>>
>> But my problem is that when i do svn log in new branch
>> location..it shows me path still of old branch
>>
>>
>> The old location is part of the history of the folder. As new
>> changes appear in the new location, those changes will
>> show the
>> new path. Older changes that happened in the older
>> location will
>> show the old path.
>>
>> Perhaps you're using something other than the command line
>> client?
>> Perhaps the UI is making this confusing?
>>
>> svn log has a "--stop-on-copy" option that will show you the
>> history of the changes only in the current location.
>>
>> I want history for this new branch to change as per
>> new branch
>> path..so that even in case the old branch gets deleted..i
>> might be able to view the changes showing in svn log
>> by going
>> to the path
>>
>> Subversion will not lose your older changes, even if you
>> delete
>> the old path. All that deleting the old path does is
>> remove the
>> reference to the contents for current and future versions
>> of the
>> parent folder. Older versions of the parent folder still
>> contain
>> the older version of the child folder.
>>
>> You might benefit from understanding the difference
>> between the
>> "peg" and "operative" versions.
>>
>> http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
>> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>
>> <http://svnbook.red-bean.com/
>> en/1.7/svn.advanced.pegrevs.html
>> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>>
>>
>> Eric.
>>
>>
>>
>>
>
Re: Svn branching issue
Posted by Eric Johnson <er...@tibco.com>.
On 11/7/16 10:10 AM, gyanendra ojha wrote:
>
> Ok so u mean ..there is no way out for this..no solution
>
Maybe, maybe not. It isn't clear whether your concern is about losing
history, or that Subversion doesn't let you rewrite history to reflect
some arbitrary desired state.
Subversion won't lose history.
Eric.
>
> On 7 Nov 2016 23:37, "Eric Johnson" <eric@tibco.com
> <ma...@tibco.com>> wrote:
>
> On 11/7/16 9:58 AM, gyanendra ojha wrote:
>
> hi eric,
>
> that is the issue, new branch created from old location is
> having the old path in svn log,i want it to point it to newly
> created branch path
>
> for example there is svn old branch //depot/a/a.txt
>
> now if i create branch //depot/b from old branch
>
> it will have a.txt in b branch..but when i go to
> //depot/b/a.txt and at GUI of SVN..do right click and select
> show log option..it shows history of changes done in
> a.txt but
> in path section it still shows //depot/a/a.txt instead of
> //depot/b/a.txt..now if old branch gets deleted..this history
> will be irrelevant for me
>
>
> As I said I in my previous response, you should review info on peg
> & operative revisions.
>
> Also, even if you delete //depot/a/ , the history of //depot/a
> persists, it is just not accessible when "peg" revision is "HEAD".
>
>
> requirement is to move a/a.txt to new location b/a.txt with
> history retained and that history should have changes pointing
> to new location b/a.txt not a/a.txt
>
>
> With Subversion, you cannot have the history changes pointing to
> the new location after your move, because that would not reflect
> the actual history! That would be re-writing history as if folder
> "a" never existed.
>
> Eric.
>
>
> i hope now u understand my issue
>
> On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson <eric@tibco.com
> <ma...@tibco.com> <mailto:eric@tibco.com
> <ma...@tibco.com>>> wrote:
>
>
> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>
>
> Hi,
>
> I was assigned a task to move a branch or folder to
> different
> location in svn
>
> Making sure that history of the old branch is retained
> and not
> lost
>
> I was able to do it and history was showing in even
> new branch
>
> But my problem is that when i do svn log in new branch
> location..it shows me path still of old branch
>
>
> The old location is part of the history of the folder. As new
> changes appear in the new location, those changes will
> show the
> new path. Older changes that happened in the older
> location will
> show the old path.
>
> Perhaps you're using something other than the command line
> client?
> Perhaps the UI is making this confusing?
>
> svn log has a "--stop-on-copy" option that will show you the
> history of the changes only in the current location.
>
> I want history for this new branch to change as per
> new branch
> path..so that even in case the old branch gets deleted..i
> might be able to view the changes showing in svn log
> by going
> to the path
>
> Subversion will not lose your older changes, even if you
> delete
> the old path. All that deleting the old path does is
> remove the
> reference to the contents for current and future versions
> of the
> parent folder. Older versions of the parent folder still
> contain
> the older version of the child folder.
>
> You might benefit from understanding the difference
> between the
> "peg" and "operative" versions.
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>
>
> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>>
>
> Eric.
>
>
>
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
Ok so u mean ..there is no way out for this..no solution
On 7 Nov 2016 23:37, "Eric Johnson" <er...@tibco.com> wrote:
> On 11/7/16 9:58 AM, gyanendra ojha wrote:
>
>> hi eric,
>>
>> that is the issue, new branch created from old location is
>> having the old path in svn log,i want it to point it to newly
>> created branch path
>>
>> for example there is svn old branch //depot/a/a.txt
>>
>> now if i create branch //depot/b from old branch
>>
>> it will have a.txt in b branch..but when i go to
>> //depot/b/a.txt and at GUI of SVN..do right click and select
>> show log option..it shows history of changes done in a.txt but
>> in path section it still shows //depot/a/a.txt instead of
>> //depot/b/a.txt..now if old branch gets deleted..this history
>> will be irrelevant for me
>>
>
> As I said I in my previous response, you should review info on peg &
> operative revisions.
>
> Also, even if you delete //depot/a/ , the history of //depot/a persists,
> it is just not accessible when "peg" revision is "HEAD".
>
>>
>> requirement is to move a/a.txt to new location b/a.txt with
>> history retained and that history should have changes pointing
>> to new location b/a.txt not a/a.txt
>>
>
> With Subversion, you cannot have the history changes pointing to the new
> location after your move, because that would not reflect the actual
> history! That would be re-writing history as if folder "a" never existed.
>
> Eric.
>
>>
>> i hope now u understand my issue
>>
>> On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson <eric@tibco.com <mailto:
>> eric@tibco.com>> wrote:
>>
>>
>> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>>
>>
>> Hi,
>>
>> I was assigned a task to move a branch or folder to different
>> location in svn
>>
>> Making sure that history of the old branch is retained and not
>> lost
>>
>> I was able to do it and history was showing in even new branch
>>
>> But my problem is that when i do svn log in new branch
>> location..it shows me path still of old branch
>>
>>
>> The old location is part of the history of the folder. As new
>> changes appear in the new location, those changes will show the
>> new path. Older changes that happened in the older location will
>> show the old path.
>>
>> Perhaps you're using something other than the command line client?
>> Perhaps the UI is making this confusing?
>>
>> svn log has a "--stop-on-copy" option that will show you the
>> history of the changes only in the current location.
>>
>> I want history for this new branch to change as per new branch
>> path..so that even in case the old branch gets deleted..i
>> might be able to view the changes showing in svn log by going
>> to the path
>>
>> Subversion will not lose your older changes, even if you delete
>> the old path. All that deleting the old path does is remove the
>> reference to the contents for current and future versions of the
>> parent folder. Older versions of the parent folder still contain
>> the older version of the child folder.
>>
>> You might benefit from understanding the difference between the
>> "peg" and "operative" versions.
>>
>> http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
>> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>
>>
>> Eric.
>>
>>
>>
>
Re: Svn branching issue
Posted by Eric Johnson <er...@tibco.com>.
On 11/7/16 9:58 AM, gyanendra ojha wrote:
> hi eric,
>
> that is the issue, new branch created from old location is
> having the old path in svn log,i want it to point it to newly
> created branch path
>
> for example there is svn old branch //depot/a/a.txt
>
> now if i create branch //depot/b from old branch
>
> it will have a.txt in b branch..but when i go to
> //depot/b/a.txt and at GUI of SVN..do right click and select
> show log option..it shows history of changes done in a.txt but
> in path section it still shows //depot/a/a.txt instead of
> //depot/b/a.txt..now if old branch gets deleted..this history
> will be irrelevant for me
As I said I in my previous response, you should review info on peg &
operative revisions.
Also, even if you delete //depot/a/ , the history of //depot/a persists,
it is just not accessible when "peg" revision is "HEAD".
>
> requirement is to move a/a.txt to new location b/a.txt with
> history retained and that history should have changes pointing
> to new location b/a.txt not a/a.txt
With Subversion, you cannot have the history changes pointing to the new
location after your move, because that would not reflect the actual
history! That would be re-writing history as if folder "a" never existed.
Eric.
>
> i hope now u understand my issue
>
> On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson <eric@tibco.com
> <ma...@tibco.com>> wrote:
>
>
> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>
>
> Hi,
>
> I was assigned a task to move a branch or folder to different
> location in svn
>
> Making sure that history of the old branch is retained and not
> lost
>
> I was able to do it and history was showing in even new branch
>
> But my problem is that when i do svn log in new branch
> location..it shows me path still of old branch
>
>
> The old location is part of the history of the folder. As new
> changes appear in the new location, those changes will show the
> new path. Older changes that happened in the older location will
> show the old path.
>
> Perhaps you're using something other than the command line client?
> Perhaps the UI is making this confusing?
>
> svn log has a "--stop-on-copy" option that will show you the
> history of the changes only in the current location.
>
> I want history for this new branch to change as per new branch
> path..so that even in case the old branch gets deleted..i
> might be able to view the changes showing in svn log by going
> to the path
>
> Subversion will not lose your older changes, even if you delete
> the old path. All that deleting the old path does is remove the
> reference to the contents for current and future versions of the
> parent folder. Older versions of the parent folder still contain
> the older version of the child folder.
>
> You might benefit from understanding the difference between the
> "peg" and "operative" versions.
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
> <http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html>
>
> Eric.
>
>
Re: Svn branching issue
Posted by gyanendra ojha <oj...@gmail.com>.
hi eric,
that is the issue, new branch created from old location is
having the old path in svn log,i want it to point it to newly
created branch path
for example there is svn old branch //depot/a/a.txt
now if i create branch //depot/b from old branch
it will have a.txt in b branch..but when i go to
//depot/b/a.txt and at GUI of SVN..do right click and select
show log option..it shows history of changes done in a.txt but
in path section it still shows //depot/a/a.txt instead of
//depot/b/a.txt..now if old branch gets deleted..this history
will be irrelevant for me
requirement is to move a/a.txt to new location b/a.txt with
history retained and that history should have changes pointing
to new location b/a.txt not a/a.txt
i hope now u understand my issue
On Mon, Nov 7, 2016 at 10:42 PM, Eric Johnson <er...@tibco.com> wrote:
>
> On 11/6/16 10:26 PM, gyanendra ojha wrote:
>
>>
>> Hi,
>>
>> I was assigned a task to move a branch or folder to different location in
>> svn
>>
>> Making sure that history of the old branch is retained and not lost
>>
>> I was able to do it and history was showing in even new branch
>>
>> But my problem is that when i do svn log in new branch location..it shows
>> me path still of old branch
>>
>>
> The old location is part of the history of the folder. As new changes
> appear in the new location, those changes will show the new path. Older
> changes that happened in the older location will show the old path.
>
> Perhaps you're using something other than the command line client? Perhaps
> the UI is making this confusing?
>
> svn log has a "--stop-on-copy" option that will show you the history of
> the changes only in the current location.
>
> I want history for this new branch to change as per new branch path..so
>> that even in case the old branch gets deleted..i might be able to view the
>> changes showing in svn log by going to the path
>>
>> Subversion will not lose your older changes, even if you delete the old
> path. All that deleting the old path does is remove the reference to the
> contents for current and future versions of the parent folder. Older
> versions of the parent folder still contain the older version of the child
> folder.
>
> You might benefit from understanding the difference between the "peg" and
> "operative" versions.
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
>
> Eric.
>
>
Re: Svn branching issue
Posted by Eric Johnson <er...@tibco.com>.
On 11/6/16 10:26 PM, gyanendra ojha wrote:
>
> Hi,
>
> I was assigned a task to move a branch or folder to different location
> in svn
>
> Making sure that history of the old branch is retained and not lost
>
> I was able to do it and history was showing in even new branch
>
> But my problem is that when i do svn log in new branch location..it
> shows me path still of old branch
>
The old location is part of the history of the folder. As new changes
appear in the new location, those changes will show the new path. Older
changes that happened in the older location will show the old path.
Perhaps you're using something other than the command line client?
Perhaps the UI is making this confusing?
svn log has a "--stop-on-copy" option that will show you the history of
the changes only in the current location.
> I want history for this new branch to change as per new branch
> path..so that even in case the old branch gets deleted..i might be
> able to view the changes showing in svn log by going to the path
>
Subversion will not lose your older changes, even if you delete the old
path. All that deleting the old path does is remove the reference to the
contents for current and future versions of the parent folder. Older
versions of the parent folder still contain the older version of the
child folder.
You might benefit from understanding the difference between the "peg"
and "operative" versions.
http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html
Eric.
Re: Svn branching issue
Posted by Stefan Hett <st...@egosoft.com>.
Hi,
On 11/7/2016 7:26 AM, gyanendra ojha wrote:
>
> Hi,
>
> I was assigned a task to move a branch or folder to different location
> in svn
>
> Making sure that history of the old branch is retained and not lost
>
> I was able to do it and history was showing in even new branch
>
> But my problem is that when i do svn log in new branch location..it
> shows me path still of old branch
>
> I want history for this new branch to change as per new branch
> path..so that even in case the old branch gets deleted..i might be
> able to view the changes showing in svn log by going to the path
>
> Please help me out if it is possible
>
If I follow you correctly, then this wouldn't be an issue. Aka: If you
delete the old branch, requesting the log for the old path still exists
in the corresponding revision. Just make sure to specify the
operative-revision (aka: [old-path-url]@[revision]).
--
Regards,
Stefan Hett