Re: [ANNOUNCE] GIT 1.6.4-rc2

> Junio C Hamano <gitster@pobox.com> wrote:
>>  * git-svn updates, including a new --authors-prog option to map author
>>    names by invoking an external program, 'git svn reset' to unwind
>>    'git svn fetch', support for more than one branches, etc.
>
> I completely forgot the implications of a change made in commit
> 0b2af457a49e3b00d47d556d5301934d27909db8.  This change probably doesn't
> affect a lot of repos out there, but --minimize-url is no longer the
> default for new imports.
>
>
> The good thing is that access-limited repositories are easier to setup
> and import.  So if you only had access for a sub_project under the
> repository root in svn://example.com/big_project/sub_project,
> you won't need read permissions to / or /big_project, just
> /big_project/sub_project and everything under it.
>
>
> Unfortunately, this default breaks the case where a project is moved to
> a lower-level within the repository:
>
> svn://example.com/foo => svn://example.com/big_project/sub_project
>
> Without --minimize-url enabled, your clone would register
> "/big_project/sub_project" to track and not be able to find the history
> of "/foo".  With --minimize-url (the old behavior), you would've
> registered "/" to be able to track all subdirectories underneath the
> repository root (assuming the SVN repo is world-readable).
>
>
> While both cases are fairly rare, I've personally encountered the latter
> (and now broken-by-default) case more.  This is because I mainly use
> git/git svn to work on free software without read restrictions.
> However, with more and more free projects switching entirely to git,
> maybe leaving the default to be more friendly to people on restrictive
> setups will be more helpful than harmful.
>
> This change only affects the creation of new clones, existing repos
> are unaffected.
>
> Let me know if the above made sense, it's late and I nodded off
> several times while writing this.