You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Fabien Meghazi <am...@gmail.com> on 2007/11/27 09:34:26 UTC

Using only one .svn folder in repository root

Hi all,

I wonder if it's possible to use only one .svn folder in the root
repository at checkout time. A bit like GIT is doing.

Having a .svn folder in each local repository's directory can be
annoying in many cases.

If there's no such option, would it be hard to patch subversion in
order to add an option that would provide this behaviour ? Would the
patch be accepted ?



-- 
Fabien Meghazi

Website: http://www.amigrave.com
Email: agr@amigrave.com
IM: amigrave@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
"Miller, Eric" <Er...@amd.com> wrote on 11/27/2007 11:41:08 AM:
> > Some tools do not handle the "extra" .svn directories well.  They
> > either are unable to correctly ignore the contents, or even worse,
> > tend to change/delete things in it when they shouldn't.  (Think
> > Visual Studio and the .svn/_svn hack.)
> > 
> > Using the OS and copying a directory (and not ignoring) the .svn
> > directories can be dangerous if you copy from one working copy
> > directory to another.  (Yes, you shouldn't do this, but users
> > do lots of things they shouldn't.)
> 
> I'm in agreement here, but I want others to know that they shouldn't
> assume that using svn mv and svn del is *always* an option for users.
> 
> Getting support for svn in closed-source 3rd party tools that
> move/rename data can be difficult at best.

Good point.  There are alot of tools that fit into the category.

(Sorry for any HTML email in the past.  Lotus Notes appears to randomly
 revert back from Plain text format periodically...)

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Using only one .svn folder in repository root

Posted by "Miller, Eric" <Er...@amd.com>.
> Some tools do not handle the "extra" .svn directories well.  They
> either are unable to correctly ignore the contents, or even worse,
> tend to change/delete things in it when they shouldn't.  (Think
> Visual Studio and the .svn/_svn hack.)
> 
> Using the OS and copying a directory (and not ignoring) the .svn
> directories can be dangerous if you copy from one working copy
> directory to another.  (Yes, you shouldn't do this, but users
> do lots of things they shouldn't.)

I'm in agreement here, but I want others to know that they shouldn't
assume that using svn mv and svn del is *always* an option for users.

Getting support for svn in closed-source 3rd party tools that
move/rename data can be difficult at best.

Eric


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: Using only one .svn folder in repository root

Posted by John Peacock <jo...@havurah-software.org>.
Fabien Meghazi wrote:
> It's just because in some situations, I'm often annoyed by the fact
> that there is  a .svn folder in each directory of the repository. Of
> course performance will be decreased by this design, but not much that
> I would care compared to the benefit of having clean folders in my
> repository.

As someone else mentioned, the WC code is particularly hairy, so it is 
highly unlikely that any redesign of this kind will happen prior to a 
complete rewrite of the WC code (i.e. 2.x timeframe).  Among other 
things, the WC code is extremely recursive in nature, meaning that each 
folder is handled independent of the next.  That is one major reason why 
the .svn directories exist at each level.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Fabien Meghazi <am...@gmail.com>.
> What are you trying to gain by creating two different ways of how
> the admin area is handled?

It's just because in some situations, I'm often annoyed by the fact
that there is  a .svn folder in each directory of the repository. Of
course performance will be decreased by this design, but not much that
I would care compared to the benefit of having clean folders in my
repository.

> Performance would even be worse in some cases, because if you move
> a directory you'd have to keep the tree in your global .svn directory
> in sync with the working copy state.

Do you mean when moving in the os or when "svn move" ?

-- 
Fabien Meghazi

Website: http://www.amigrave.com
Email: agr@amigrave.com
IM: amigrave@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Using only one .svn folder in repository root

Posted by "Miller, Eric" <Er...@amd.com>.
> What are you trying to gain by creating two different ways of how
> the admin area is handled?
> 
> In your proposal, the top-level .svn directory mirrors the working
> copy anyway, so your goal cannot be to improve performance.

How about removing the issues of .svn/ corruption, removal, etc that can
occur at every level of the working copy?  I value reliability and
robustness of the working copy far more than performance, and that
robustness just isn't there right now.

Eric


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


RE: Re: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
"Reedick, Andrew" <jr...@ATT.COM> wrote on 11/27/2007 03:06:37 PM:
> > -----Original Message-----
> > From: Joachim Durchholz [mailto:jo@durchholz.org] 
> > Sent: Tuesday, November 27, 2007 3:41 PM
> > To: Subversion Users
> > Subject: Re: Using only one .svn folder in repository root
> > 
> > kmradke@rockwellcollins.com schrieb:
> > > Hmm... How about a third option:
> > > 
> > > Just a single .svn file in each directory that points to 
> > the location 
> > > of the working copy meta data location.  This has other 
> > ramifications 
> > > I'm sure no one has thought about yet.
> > 
> > That would still have problems with tools that get confused 
> > by extraneous files.
> > Though at least the Search function of the Windows Explorer 
> > would be less cluttered with irrelevant results.
> > 
> 
> Wouldn't flagging the .svn file/dir as being a hidden and/or system file
> cause the search results and explorer to ignore it?

Depending upon the tool, possibly.  However, hiding the directory is
inviting users to be unaware the directory exists, causing them
to unexpectedly copy the directory to places they shouldn't.

I.E. I've had users use windows explorer and copy some directories
from one working copy to another for another repo.  Then they will
get strange errors when they try and add the dirs to the new repo.

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Re: Using only one .svn folder in repository root

Posted by "Reedick, Andrew" <jr...@ATT.COM>.
 

> -----Original Message-----
> From: Joachim Durchholz [mailto:jo@durchholz.org] 
> Sent: Tuesday, November 27, 2007 3:41 PM
> To: Subversion Users
> Subject: Re: Using only one .svn folder in repository root
> 
> kmradke@rockwellcollins.com schrieb:
> > Hmm... How about a third option:
> > 
> > Just a single .svn file in each directory that points to 
> the location 
> > of the working copy meta data location.  This has other 
> ramifications 
> > I'm sure no one has thought about yet.
> 
> That would still have problems with tools that get confused 
> by extraneous files.
> Though at least the Search function of the Windows Explorer 
> would be less cluttered with irrelevant results.
> 

Wouldn't flagging the .svn file/dir as being a hidden and/or system file
cause the search results and explorer to ignore it?

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


Re: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
Joachim Durchholz <jo...@durchholz.org> wrote on 11/27/2007 02:41:29 PM:

> kmradke@rockwellcollins.com schrieb:
> > Hmm... How about a third option:
> > 
> > Just a single .svn file in each directory that points to the location
> > of the working copy meta data location.  This has other ramifications 
I'm
> > sure no one has thought about yet.
> 
> That would still have problems with tools that get confused by 
> extraneous files.
> Though at least the Search function of the Windows Explorer would be 
> less cluttered with irrelevant results.

Yes, it obviously doesn't solve all the problems, but simple searches
was an example I'm thinking of.  Tools typically can ignore a single
named file easier than a directory full of similarly named files too.

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Joachim Durchholz <jo...@durchholz.org>.
kmradke@rockwellcollins.com schrieb:
> Hmm... How about a third option:
> 
> Just a single .svn file in each directory that points to the location
> of the working copy meta data location.  This has other ramifications I'm
> sure no one has thought about yet.

That would still have problems with tools that get confused by 
extraneous files.
Though at least the Search function of the Windows Explorer would be 
less cluttered with irrelevant results.

Regards,
Jo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
Joachim Durchholz <jo...@durchholz.org> wrote on 11/27/2007 11:51:09 AM:
> kmradke@rockwellcollins.com schrieb:
> >> with a root .svn, traverse up the directory hierarchy to find the 
.svn. 
> >> This *could* slow the Windows Explorer down, since it will call into 
SVN 
> >> whenever you look at the properties of a file - though the slowdown 
> >> would be negligible if SVN cached the whereabouts of all .svn 
> >> directories (though I'd want the caching code to shake out a few more 

> >> bugs before doing that, the left pane of Windows Explorer still 
doesn't 
> >> update properly for me).
> > 
> > Oh, I was thinking at the root of the tree, not completely outside the
> > tree.  I didn't explain that well.
> 
> That wouldn't change anything.
> See, whenever Windows Explorer shows the Properties dialog of a file, or 

> its context menu, it calls into the SVN hook dll.
> To do the right thing, the SVN dll has to decide whether that file is, 
> in fact, part of a checked-out repository tree (for the Properties 
> dialog, it's the decision whether the 'Subversion' tab should appear, 
> for the context menu, it's the decision which of two variants of the 
> context menu should be shown).
> To find out whether the file is part of such a repository tree, the SVN 
> dll would have to traverse the directory tree up to the root to see 
> whether there's a .svn directory somewhere. This check would have to 
> happen for every file in the Windows directory; in fact the check would 
> require more disk accesses for non-repository files, because then the 
> search would go all the way up to the root directory.
> 
> Windows Explorer is the primary means of accessing files, and if such a 
> lookup has any noticeable performance impact on Windows explorer, that 
> would be a heavy factor against the use of TSVN.
> To check that out, somebody would have to add some directory traversal 
> code to TSVN and check it out on a machine with marginal performance. 
> You'd also want to lose a few thoughts about where exactly the search 
> should end - there's stuff like network drives, the Desktop, etc., which 

> don't have the exact Posix semantics of a filesystem directory.
> 
> BTW this might also have ramifications for the handling of the 
> svn:externals property.
> 
> Note that I won't speak for or against such a feature. It's just that 
> these problems should be solved before rolling it out to the general 
public.
> 
> However, if I were a project leader, I'd flatly refuse to implement 
> this. Too many potential sources of trouble, and I'd prefer a slightly 
> awkward TSVN to one that occasionally loses data or slows down Windows 
> Explorer.

Hmm... How about a third option:

Just a single .svn file in each directory that points to the location
of the working copy meta data location.  This has other ramifications I'm
sure no one has thought about yet.

I'm not suggesting anything, just thinking out loud.  And I agree, if
performance or complexity is sacrificed, it is a big -1 to implement these
things.

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Joachim Durchholz <jo...@durchholz.org>.
kmradke@rockwellcollins.com schrieb:
>> with a root .svn, traverse up the directory hierarchy to find the .svn. 
>> This *could* slow the Windows Explorer down, since it will call into SVN 
>> whenever you look at the properties of a file - though the slowdown 
>> would be negligible if SVN cached the whereabouts of all .svn 
>> directories (though I'd want the caching code to shake out a few more 
>> bugs before doing that, the left pane of Windows Explorer still doesn't 
>> update properly for me).
> 
> Oh, I was thinking at the root of the tree, not completely outside the
> tree.  I didn't explain that well.

That wouldn't change anything.
See, whenever Windows Explorer shows the Properties dialog of a file, or 
its context menu, it calls into the SVN hook dll.
To do the right thing, the SVN dll has to decide whether that file is, 
in fact, part of a checked-out repository tree (for the Properties 
dialog, it's the decision whether the 'Subversion' tab should appear, 
for the context menu, it's the decision which of two variants of the 
context menu should be shown).
To find out whether the file is part of such a repository tree, the SVN 
dll would have to traverse the directory tree up to the root to see 
whether there's a .svn directory somewhere. This check would have to 
happen for every file in the Windows directory; in fact the check would 
require more disk accesses for non-repository files, because then the 
search would go all the way up to the root directory.

Windows Explorer is the primary means of accessing files, and if such a 
lookup has any noticeable performance impact on Windows explorer, that 
would be a heavy factor against the use of TSVN.
To check that out, somebody would have to add some directory traversal 
code to TSVN and check it out on a machine with marginal performance. 
You'd also want to lose a few thoughts about where exactly the search 
should end - there's stuff like network drives, the Desktop, etc., which 
don't have the exact Posix semantics of a filesystem directory.

BTW this might also have ramifications for the handling of the 
svn:externals property.

Note that I won't speak for or against such a feature. It's just that 
these problems should be solved before rolling it out to the general public.

However, if I were a project leader, I'd flatly refuse to implement 
this. Too many potential sources of trouble, and I'd prefer a slightly 
awkward TSVN to one that occasionally loses data or slows down Windows 
Explorer.

Regards,
Jo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
Joachim Durchholz <jo...@durchholz.org> wrote on 11/27/2007 11:22:21 AM:
> > If all the maintenance data was outside the normal tree, you just
> > wouldn't have to worry about any poorly designed tools.
> 
> Yes, but then you get into trouble if the user moves the checked-out 
> directory. In that case, he even loses the information which files he 
> changed, and that would be an unrecoverable error.
> 
> I could imagine putting the .svn tree at the root of the checked-out 
> repository.
> You'd lose the ability to move a subdirectory around with OS facilities 
> and retain its status as a working copy. Also, finding the .svn 
> directory that corresponds to a given file could become more 
> complicated; at the moment, just look for .svn in the current directory, 

> with a root .svn, traverse up the directory hierarchy to find the .svn. 
> This *could* slow the Windows Explorer down, since it will call into SVN 

> whenever you look at the properties of a file - though the slowdown 
> would be negligible if SVN cached the whereabouts of all .svn 
> directories (though I'd want the caching code to shake out a few more 
> bugs before doing that, the left pane of Windows Explorer still doesn't 
> update properly for me).

Oh, I was thinking at the root of the tree, not completely outside the
tree.  I didn't explain that well.

Kevin R.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Joachim Durchholz <jo...@durchholz.org>.
kmradke@rockwellcollins.com schrieb:
> Some users find all the "extra" .svn directories distracting.  (Even
> if they are hidden, etc.)
> 
> Some tools do not handle the "extra" .svn directories well.  They
> either are unable to correctly ignore the contents, or even worse,
> tend to change/delete things in it when they shouldn't.  (Think
> Visual Studio and the .svn/_svn hack.)

Granted.

> Using the OS and copying a directory (and not ignoring) the .svn
> directories can be dangerous if you copy from one working copy
> directory to another.  (Yes, you shouldn't do this, but users
> do lots of things they shouldn't.)

You can always retrieve a new directory and copy over the files you 
changed, so this kind of error is recoverable.

> If all the maintenance data was outside the normal tree, you just
> wouldn't have to worry about any poorly designed tools.

Yes, but then you get into trouble if the user moves the checked-out 
directory. In that case, he even loses the information which files he 
changed, and that would be an unrecoverable error.

I could imagine putting the .svn tree at the root of the checked-out 
repository.
You'd lose the ability to move a subdirectory around with OS facilities 
and retain its status as a working copy. Also, finding the .svn 
directory that corresponds to a given file could become more 
complicated; at the moment, just look for .svn in the current directory, 
with a root .svn, traverse up the directory hierarchy to find the .svn. 
This *could* slow the Windows Explorer down, since it will call into SVN 
whenever you look at the properties of a file - though the slowdown 
would be negligible if SVN cached the whereabouts of all .svn 
directories (though I'd want the caching code to shake out a few more 
bugs before doing that, the left pane of Windows Explorer still doesn't 
update properly for me).

Just my 2c,
Jo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by km...@rockwellcollins.com.
Stefan Sperling <st...@elego.de> wrote on 11/27/2007 11:00:05 AM:
> On Tue, Nov 27, 2007 at 05:40:40PM +0100, Fabien Meghazi wrote:
> > > It is not possible to do this today. It would be a major rewrite of
> > > the client libraries to do this.
> > 
> > I didn't realized it would required so much work. I was thinking about
> > a patch that would simply change behaviour of svn command like this :
> > 
> > Pseudo Code
> 
> >  6.         if .svn folder is "marked" as "single .svn mode"
> >  7.             # we are in the root of a "single .svn" repository
> >  8.             set some variable state for further patching
> >  9.         else
> > 10.             # we are in a standard (not single .svn) repository
> > 11.             set some variable state for further patching
> > 12.         end if
> 
> What are you trying to gain by creating two different ways of how
> the admin area is handled?
> 
> In your proposal, the top-level .svn directory mirrors the working
> copy anyway, so your goal cannot be to improve performance.

Some users find all the "extra" .svn directories distracting.  (Even
if they are hidden, etc.)

Some tools do not handle the "extra" .svn directories well.  They
either are unable to correctly ignore the contents, or even worse,
tend to change/delete things in it when they shouldn't.  (Think
Visual Studio and the .svn/_svn hack.)

Using the OS and copying a directory (and not ignoring) the .svn
directories can be dangerous if you copy from one working copy
directory to another.  (Yes, you shouldn't do this, but users
do lots of things they shouldn't.)

If all the maintenance data was outside the normal tree, you just
wouldn't have to worry about any poorly designed tools.

I would hate to make the working copy code any more complex though...

You may want to take a look at SVK, which is built upon the svn libs, but
does not clutter the working copy with .svn directories, instead it
includes a whole copy of the repo in a separate area.

Kevin R.

Re: Using only one .svn folder in repository root

Posted by Stefan Sperling <st...@elego.de>.
On Tue, Nov 27, 2007 at 05:40:40PM +0100, Fabien Meghazi wrote:
> > It is not possible to do this today. It would be a major rewrite of
> > the client libraries to do this.
> 
> I didn't realized it would required so much work. I was thinking about
> a patch that would simply change behaviour of svn command like this :
> 
> Pseudo Code
 
>  6.         if .svn folder is "marked" as "single .svn mode"
>  7.             # we are in the root of a "single .svn" repository
>  8.             set some variable state for further patching
>  9.         else
> 10.             # we are in a standard (not single .svn) repository
> 11.             set some variable state for further patching
> 12.         end if

What are you trying to gain by creating two different ways of how
the admin area is handled?

In your proposal, the top-level .svn directory mirrors the working
copy anyway, so your goal cannot be to improve performance.

Performance would even be worse in some cases, because if you move
a directory you'd have to keep the tree in your global .svn directory
in sync with the working copy state.

I recommend you read the subversion/libsvn_wc/README file if you
have not read it already. It explains a lot of the reasons behind
the current design. Some shortcomings of the current design are
documented in notes/wc-improvements.

AFAIK the idea of a global .svn directory has been coined before,
but more in a context of a general working copy redesign/rewrite,
instead of adding additional complexity to an already complex
library -- libsvn_wc is, at least according to Karl Fogel and Michael
Pilato who told me this in person, one of the most complex areas
in the subversion code that few developers want to mess with.

-- 
Stefan Sperling <st...@elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner

Re: Using only one .svn folder in repository root

Posted by Fabien Meghazi <am...@gmail.com>.
> It is not possible to do this today. It would be a major rewrite of
> the client libraries to do this.

I didn't realized it would required so much work. I was thinking about
a patch that would simply change behaviour of svn command like this :

Pseudo Code

 1.  when an svn operation is fired
 2.     if .svn folder is present in folder the operation is bound to
 3.         # look inside this .svn folder and see if there's
 4.         # a "mark" indicating that the mode of this
 5.         # repository is in "single .svn folder"
 6.         if .svn folder is "marked" as "single .svn mode"
 7.             # we are in the root of a "single .svn" repository
 8.             set some variable state for further patching
 9.         else
10.             # we are in a standard (not single .svn) repository
11.             set some variable state for further patching
12.         end if
13.     else
14.         while i can access to a parent directory
15.             if a .svn folder is found in current loop directory
AND .svn folder is "marked" as "single .svn mode"
16.                 we found the .svn root
17.             end if
18.         end while
19.         if .svn root was found
20.             set some variable state for further patching
21.         else
22.             no working copy found. end
23.         end if
24.     end if
25.  end when


The single .svn folder in the root of the repository would have a
"replication" of the project's directory structure.

Eg:

|- [Dir] Mydir1
|       |- [Dir] Mysubdir 1
|       |- [Dir] Mysubdir 2
|       |- File 1
|       |- File 2
|- [Dir] Mydir2
|- [Dir] .svn
|       |- [Dir] Mydir1
|       |       |- [Dir] .svn (Usual .svn stuff : prop-base, ...) FOR Mydir1
|       |       |- [Dir] Mysubdir 1
|       |       |       |- [Dir] .svn (Usual .svn stuff : prop-base,
...) FOR Mysubdir1
|       |       |- [Dir] Mysubdir 2
|       |       |       |- [Dir] .svn (Usual .svn stuff : prop-base,
...) FOR Mysubdir2
|       |- [Dir] Mydir2
|       |       |- [Dir] .svn (Usual .svn stuff : prop-base, ...) FOR Mydir2
|       |- [Dir] .svn (Usual .svn stuff : prop-base, ...) FOR repository root


The variable states kept in the here-before pseudo code will help to
patch svn logic for places in the code where we need the svn data for
a particular folder.
So, instead of searching in ./.svn/* (when action is done on folder
"Mydir1") it will search svn data in
"<repository_root_previously_found>/.svn/Mydir1/.svn/*"
same for svn move, svn add, svn delete, ...

Never looked at the svn source, but if the .svn folder to be used for
a given operation is computed at a unique place, then the second part
of the patch would go there.

As the implementation would be added as an option to "svn checkout",
it won't break anything. And third party projects could decide to
implement the new feature or not.

Bonus: convertion between a normal repository and a "single .svn"
repository (and vice versa) is very easy as it just imply
moving/create folders from one place to another.


So, as always, I guess that I forgot something very important that
would make my idea not doable. Do you have something in mind about
this ? Cause if nothing makes this patch silly, I guess it could be
quickly done, without needing a major rewrite of client libs.


-- 
Fabien Meghazi

Website: http://www.amigrave.com
Email: agr@amigrave.com
IM: amigrave@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 27, 2007, at 03:34, Fabien Meghazi wrote:

> I wonder if it's possible to use only one .svn folder in the root
> repository at checkout time. A bit like GIT is doing.
>
> Having a .svn folder in each local repository's directory can be
> annoying in many cases.
>
> If there's no such option, would it be hard to patch subversion in
> order to add an option that would provide this behaviour ? Would the
> patch be accepted ?

It is not possible to do this today. It would be a major rewrite of  
the client libraries to do this. I believe the developers are already  
planning something like this but there is no ETA.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Fabien Meghazi <am...@gmail.com>.
> One option might be to try out FSVS - which uses SVN for back-end
> storage but doesn't create .svn folders.  FSVS is designed for
> versioning files like the contents of /etc or whatever else you want to
> keep track of on a unix server's file system.

Thanks but I'm now using git-svn as client, it fits my needs.

-- 
Fabien Meghazi

Website: http://www.amigrave.com
Email: agr@amigrave.com
IM: amigrave@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Using only one .svn folder in repository root

Posted by Thomas Harold <tg...@tgharold.com>.
Fabien Meghazi wrote:
> Hi all,
> 
> I wonder if it's possible to use only one .svn folder in the root
> repository at checkout time. A bit like GIT is doing.

One option might be to try out FSVS - which uses SVN for back-end 
storage but doesn't create .svn folders.  FSVS is designed for 
versioning files like the contents of /etc or whatever else you want to 
keep track of on a unix server's file system.

(The main reason that SVN uses .svn folders is because CVS used a 
similar system, and SVN is a better version of CVS.)

Personally, I'm on the fence about .svn folders.  In a lot of ways, it's 
a good setup, but there are other days when I don't like the extra 
folders.  It's something that we've learned to live with and SVN is 
still a lot better then our old version control system.

(If I could set a flag that tells SVN not to keep pristine local copies 
of certain types of files... I'd be happier.)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org