Abdelrazak Younes <you...@lyx.org> writes:
| Lars Gullik Bjønnes wrote:
>> Abdelrazak Younes <you...@lyx.org> writes:
>>
>> [...]
>> | No, AFAIK you can clone a git repo with 'git clone' and then use
>> | git-svn for the rest. I use Pavel's LyX repo for history and blaming
>> | with qgit and that's very very good compared to 'svn log' and 'svn
>> | blame', even more important, that's fast, incredibly fast!
>> | But I still don't use git-svn for commit...
>>
>> Then you are loosing out imho.
>>
| Well git-svn was not available under windows (with mysgit) and, last
| time I tried under Linux (during the meething), I didn't manage to use
| it with ssh. Well, to tell the truth, Pavel didn't manage ;-)
That's why a cookbook would be nice. Btw I have working, git svn rebase
to update over ssh. Sure I have not tried a dcommit yet, but I am
confident that will just work.
>> | Quite frankly, and IMHO, if a change to git is wanted, I'd prefer that
>> | we switch to a git repo altogether. We should declare a git repository
>> | somewhere *the main repository* and don't force the use of git-svn. If
>> | some developpers can't switch immediately, I'd suggest that we
>> | maintain an svn server that is periodically pushed to the git main
>> | repo.
>>
>> Sure if a change is wanted we will go the full 10 yards... but why
>> unwilling to gain experience by testing with git-svn first?
>>
>
| Oh, I already use an like git. But I am affraid most developpers won't
| use it if svn is still available.
Right... _that_ is why we should be it really easy to test it out with
git-svn... not just for browsing logs and doing blame but for commits
as well.
When git stash, git rebase -i and the like is discovered I'd be almost
surprised if anyone would want to go back.
--
Lgb
