Le 26/05/2013 19:53, Gary Gregory a écrit : > Or... We could switch from svn to git.
+1 from me. I have been using git for quite some time now and am particularly happy with it (well I was also happy when I switched from SCCS to RCS to CVS to SVN, and will probably also like what the next generation will bring after Git). One drawback, though, is that it needs some time to get used to it. We should really have a large number of committers in favor of such a change to do it. Just in order to have a rough idea, how many of us already use Git, how many don't use it but would like to give it a try, and how many don't want it? I'm not sure if we could switch only some components first and the other ones later on. As we already have a specific layout with two layers (proper/sandbox/dormant) and then all the components, it may need some tricks and help from infra. Luc > I know, I know, I don't want > to start another 1000 message long thread. ;) > > Gary > > On May 26, 2013, at 13:06, Oliver Heger <oliver.he...@oliver-heger.de> wrote: > >> Hi Luc, >> >> Am 25.05.2013 21:53, schrieb Luc Maisonobe: >>> Le 25/05/2013 21:16, Oliver Heger a écrit : >>>> Hi all, >>> >>> Hi Oliver, >>> >>>> >>>> recently I switched from svn to git and now use git svn to do my commits. >>>> >>>> One problem I have with this setup is that git svn does not honor the >>>> autoprops configured for svn. Therefore, all newly added files are >>>> missing these properties. >>>> >>>> I think I am not the only git user here. So I would like to ask how >>>> others address this problem. >>> >>> This is the setting I have been used for months (probably more than one >>> year). >>> >>> This seems strange to me, I thought git svn honoured the autoprops. >>> Looking back at a commit where I created lots of newx files (like >>> <http://markmail.org/message/4yb4yzp2ixqvhl2e>), the properties where >>> set properly. So I think it works for me. In my case, I work on Linux >>> and the subversion properties are set in a file $HOME/.subversion/config. >>> >>> There is also one specific property that may need to be set specifically >>> for git, it is the line-endings encoding. On a Linux machine, I globally >>> set "core.autocrlf" ot "input" (the setting must be different for Windows). >> thanks for your answer. Hm, it may be an OS-specific issue then (I am on >> Windows). >> >> I found contradictory information on the net. While some say svn >> autoprops would work, there is the following statement in [1] (which >> should be the reference) in the "Bugs" section: >> >> "We ignore all SVN properties except svn:executable." >> >> Will have to do some more research, but currently I even don't know >> whether this is supposed to work :-( If somebody has a working >> configuration for Windows, please let me know! >> >> Thanks >> Oliver >> >> [1] https://www.kernel.org/pub/software/scm/git/docs/git-svn.html >> >>> Luc >>> >>> >>>> >>>> Thanks in advance! >>>> Oliver >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
