On Thu, Oct 27, 2016 at 4:04 PM, Dario Niedermann wrote:
> I have a repository I had made in a pinch, without any directory
> structure, just adding files to the root.
>
> When the time came to add some method to the madness, I created
> the 3 canonical directories, then moved (server-side) all fi
On 10/27/16 7:04 AM, Dario Niedermann wrote:
I have a repository I had made in a pinch, without any directory
structure, just adding files to the root.
When the time came to add some method to the madness, I created
the 3 canonical directories, then moved (server-side) all files to
'trunk/'. No
On Mon, Jun 17, 2013 at 4:09 PM, Olivier Antoine
wrote:
>
>> The common scenario is to have multiple 'projects' under the same
>> repository root, each with their own trunk/branches/tags tree.
>
> To be honest, I'm afraid of several projects sharing a same revision
> numbering.
> Repository gets b
Hi,
>>> From: Ryan Schmidt
> On the other hand, let's say you've made changes and tested them and try
to commit and it fails because a file is out of date.
> You wish you had made a feature branch for these changes. No problem; you
can still do it now.
> Use "svn info" on the working copy to fin
On Sun, Jun 16, 2013 at 3:55 PM, Olivier Antoine
wrote:
>
> >Taking the history in a copy is what makes svn work and it makes any
>> copied directory functionally usable as a branch or tag. But after
>> that it depends on how you actually use it...
>
> As consequence, SVN allows to create branch
On Jun 16, 2013, at 15:55, Olivier Antoine wrote:
> When you commit, commit can fail, and you might have to merge before
> committing.
If you commit, and the commit fails because one or more of the files you
changed was also changed in the repository, then you have to "svn update" the
working
Thanks, that's a lot to think about,
>>> From: Les Mikesell
>Taking the history in a copy is what makes svn work and it makes any
> copied directory functionally usable as a branch or tag. But after
> that it depends on how you actually use it...
As consequence, SVN allows to create branches a
On Fri, 14 Jun 2013 12:55:11 +, Andrew Reedick wrote:
...
> Back in my day, CC snapshot views were terrible/horrible/nearly_unusable.
> SVN workspaces are simply great. I doubt your users will complain once they
> start using them.
There is one thing that potentially can cause a *lot* of p
> From: Olivier Antoine [mailto:oliviera201...@gmail.com]
> Sent: Thursday, June 13, 2013 3:57 PM
> To: users@subversion.apache.org
> Subject: Re: History in subversion
>
>
> Thanks All again for your help,
>
>
> > If you're just trying to find a f
On Thu, 13 Jun 2013 21:57:17 +, Olivier Antoine wrote:
...
> I think that dynamic view is still a nice concept. Dynamic views is
> something that users like much, and they desespair when they have to
> migrate to snapshot views.
> You create your view, you have an (almost) real-time connection
On Thu, 13 Jun 2013 16:23:39 +, Les Mikesell wrote:
...
> > Revision numbers can be renumbered one day in the repository, so they cannot
> > be used in the SCM process, am I wrong ?
>
> No, revisions can never be renumbered in an existing repository. It
> is possible to dump the repository a
On Thu, Jun 13, 2013 at 2:57 PM, Olivier Antoine
wrote:
>
> A good SCM principe is :
> - to create tag on branch
> - to create branch from tag
>
I think most people settle on one of two basic 'styles'. The
'dirty-trunk' style makes the most sense to me where most development
happens on the trun
Thanks All again for your help,
>>> From: Les Mikesell
>> I did not understand everything with branches and tags, I have to read
again
>> the manual, but I have the feeling that branches and tags are not linked,
>> this is strange to me.
> Linked to what? Think of them as 'cheap copies' of wha
On Wed, Jun 12, 2013 at 10:45 PM, Les Mikesell wrote:
> On Wed, Jun 12, 2013 at 2:41 PM, Olivier Antoine
> wrote:
...
>> Could you help more on diff dirs, please :
>> - What is the best way with SVN to compare a same directory on two different
>> branches ?
>
> Just check one out and diff the wor
> From: Olivier Antoine [mailto:oliviera201...@gmail.com]
> Sent: Wednesday, June 12, 2013 3:42 PM
> To: users@subversion.apache.org
> Subject: Re: History in subversion
>
> Thanks All for your help and advices,
> But :
>
> With CC, I can easily search for any file e
On Wed, Jun 12, 2013 at 2:41 PM, Olivier Antoine
wrote:
> >
> Ok, svn log -v will help,
>
> But :
>
> With CC, I can easily search for any file element in a repository, and
> directly get its path,
> With SVN, I have to check all revisions, then I can know where this element
> is located in the re
Thanks All for your help and advices,
>> From: Les Mikesell :
> svn logs will show file/directory additions/deletions in the parent
directory, so you should be able to track the history of things that way if
you wanted, but what is it that you specifically need to do?
> Most people would just chec
On Jun 11, 2013, at 15:45, Olivier Antoine wrote:
> But this is very poor compared to ClearCase. Nobody tried to script that ?
Most of us have never seen or used ClearCase. It might help if you provided a
specific example of a command that you might run with ClearCase, and the output
you would
> From: Olivier Antoine [mailto:oliviera201...@gmail.com]
> Sent: Tuesday, June 11, 2013 4:45 PM
> To: users@subversion.apache.org
> Subject: Re: History in subversion
>
> Thanks for your help, I will try again this.
> But this is very poor compared to ClearCase. Nobody trie
> From: Olivier Antoine [mailto:oliviera201...@gmail.com]
> Sent: Tuesday, June 11, 2013 13:45
> To: users@subversion.apache.org
> Subject: Re: History in subversion
>
> Thanks for your help, I will try again this.
> But this is very poor compared to ClearCase. Nobody
On Tue, Jun 11, 2013 at 3:45 PM, Olivier Antoine
wrote:
> Thanks for your help, I will try again this.
>
> But this is very poor compared to ClearCase. Nobody tried to script that ?
svn logs will show file/directory additions/deletions in the parent
directory, so you should be able to track the h
On Tue, Jun 11, 2013 at 4:45 PM, Olivier Antoine
wrote:
> Thanks for your help, I will try again this.
>
> But this is very poor compared to ClearCase. Nobody tried to script that ?
It is open-source, so nothing is stopping someone from implementing
this if they find it important. I think most o
Thanks for your help, I will try again this.
But this is very poor compared to ClearCase. Nobody tried to script that ?
It is also possible to read the SVN repository without checkout, there is a
way to address an element, something like this :
@revnumber
But it is not possible to use a syntax l
On Tue, Jun 11, 2013 at 4:02 PM, Olivier Antoine
wrote:
> I don't think that svn log describes the history of the directory element,
OK, did not pick up that you were only interested in that information.
You are right that SVN will always show the information for directory
plus children. The o
I don't think that svn log describes the history of the directory element,
Actually I don't see any command that could give the revisions where the
directory changed (tree changes), without giving the changes on the files
it contents. No svn+annotate on directories.
And I don't see any way to app
On Tue, Jun 11, 2013 at 3:15 PM, Olivier Antoine
wrote:
> I'm trying to work with SVN, but coming from ClearCase, I'm lost.
>
> It seems that it is not possible to consult the history of the repository
> like in CC,
> I can get the history of a file element with svn+annotate, I can use
> svn+diff
Klaus Ganser wrote on Thu, Nov 11, 2010 at 13:09:51 -0800:
> It would be nice for this feature to see the light of day.
For this, we'll need a design that makes it possible to answer the
query efficiently.
Feel free to submit one; our documentation is in the text files
subversion/libsvn_fs_base/n
On Thu, Nov 11, 2010 at 5:17 AM, Johan Corveleyn wrote:
> So, as far as I'm concerned, I think you can file this as a new
> feature request in the issue tracker (maybe first search for any
> similar outstanding requests).
Filed the bug here:
http://subversion.tigris.org/issues/show_bug.cgi?id=3
On Wed, Nov 10, 2010 at 9:53 PM, Feldhacker, Chris
wrote:
> -Original Message-
> From: Klaus Ganser [mailto:kgan...@gmail.com]
> Sent: Wednesday, November 10, 2010 2:43 PM
> To: Feldhacker, Chris
> Cc: users@subversion.apache.org
> Subject: Re: History of a fixed path
-Original Message-
From: Klaus Ganser [mailto:kgan...@gmail.com]
Sent: Wednesday, November 10, 2010 2:43 PM
To: Feldhacker, Chris
Cc: users@subversion.apache.org
Subject: Re: History of a fixed path across all objects
>> On Wed, Nov 10, 2010 at 12:19 PM, Feldhacker, Chris
>
On Wed, Nov 10, 2010 at 12:19 PM, Feldhacker, Chris
wrote:
> I think you want the "--ignore-ancestry" option:
svn log does not support that option.
On Wed, Nov 10, 2010 at 12:09 PM, Ryan Schmidt
wrote:
> Are you sure? I think what the others are trying to tell you is that the
> repository does not store this information, so there is not a way that any
> client could return this information to you without doing an exhaustive
> search.
I k
On 11/10/2010 2:05 PM, Klaus Ganser wrote:
On Wed, Nov 10, 2010 at 11:48 AM, Les Mikesell wrote:
If something is deleted and recreated there is no history connecting them
even if those things have the same name, so what you are asking for doesn't
really exist. Maybe you could 'svn log -v' a pa
apache.org
Subject: Re: History of a fixed path across all objects
On Wed, Nov 10, 2010 at 11:32 AM, David Weintraub wrote:
> You want the entire history of a file called "bar.java" in the path
> /foo/bar/barfoo from revision #1 to the current revision -- even
> though it is
On Nov 10, 2010, at 14:05, Klaus Ganser wrote:
> It would be absurd if the command to generate a
> view of this one path took as long as the command to view the history
> of the entire repository. I'm saying that this is a valid use-case
> that the svn cli does not currently satisfy, but one whi
On Wed, Nov 10, 2010 at 11:48 AM, Les Mikesell wrote:
> If something is deleted and recreated there is no history connecting them
> even if those things have the same name, so what you are asking for doesn't
> really exist. Maybe you could 'svn log -v' a parent or the top level of the
> repo and
On 11/10/2010 1:22 PM, Klaus Ganser wrote:
Hello,
I originally asked this question on stackoverflow:
http://stackoverflow.com/questions/4140377/svn-log-of-a-fixed-path-across-copies-and-moves
Nobody seems to have a good solution to getting the history of a
specific path across all objects that
On Wed, Nov 10, 2010 at 11:32 AM, David Weintraub wrote:
> You want the entire history of a file called "bar.java" in the path
> /foo/bar/barfoo from revision #1 to the current revision -- even
> though it isn't the same bar.java at that location?
>
> Is this correct?
Yes, that is correct.
So, exactly what are you asking for?
I have a file /foo/bar/barfoo/bar.java.
You want the entire history of a file called "bar.java" in the path
/foo/bar/barfoo from revision #1 to the current revision -- even
though it isn't the same bar.java at that location?
Is this correct?
--
David Weintr
On Thursday 20 May 2010, AM wrote:
> We currently create release branches with version numbers (i.e. 1.3.x,
> 1.4.x).
This is reasonable and not unusual. From those branches you then create the
tags (1.3.0, 1.3.1 etc).
> If we wanted to move to a single folder for releases (say Production
> Supp
40 matches
Mail list logo
