Thanks for these answers.
I found that git does support password caching with:
git config --global credential.helper cache
but I set up an SSH key instead, as you suggested.
The branch called master was created when I did the "git svn rebase".
It was easy to remove and I won't try to update from the subversion
I notice that you mention running the git-update script. I followed the
instructions in the following link which removes the need for this.
It seems to work. Can you see any disadvantages with this approach?
I have started to look at gitk and git-gui, but I wanted to get familiar
with the command line first.
So far, from what I've seen, I can't see myself going back to subversion
On 13/12/12 22:56, John Ralls wrote:
> On Dec 13, 2012, at 2:17 PM, Nick Hall <nick__hall@...> wrote:
>> John, Benny,
>> I have created a wiki page to describing my trial of using git for
>> Gramps development:
>> Maybe others will find this useful.
>> I have some more questions though:
>> I created a single .gitignore file in the top level directory and
>> committed it.
>> 1. I was asked twice for my password. Is there any way to store this
>> as subversion does?
> Not that I know of. You should in any case not be relying on stored passwords. Instead, set up an SSH key to use with sourceforge and change the URI in .git/configure to SVN+SSH://svn.code.sf.net/...
>> 2. A branch called "master" was created. Why is this?
> Since I don't see it in SF, I guess that it was created in your git repo. That's just git's default behavior. You can either make it track origin/trunk or make a new branch "trunk" to track origin/trunk and delete "master". Totally a preference matter.
>> 3. No svn properties were set on the new file. Can I set them using
> Seems not. Git-svn's documentation discusses reading svn properties, but nothing about writing them.
>> 4. There is a "git svn create-ignore" command which creates .gitignore
>> files from subversion properties. Should we use this?
> You can if you want.
>> 5. Is it safe to use "git svn rebase" to get commits that are more
>> recent than those in the mirror? I notice that the username and email
>> address do not get translated.
> Not really. The script which maintains the mirror does some extra magic with branches and tags, as well as having an author file (which I can share if you like -- I didn't want to put it in the repo since we already have two) which will cause hashes to be different, so git won't recognize them and you'll get a messy history. It will also put git svn's pointers out of whack with respect to git-update's. You can fix it all with by git reset --hard and git svn reset to put the state back to where you last were in sync with the mirror then running git-update, but that's probably not something that you want to do routinely.
>> So far I like using git! Using it in conjunction with subversion does
>> add extra complexity though.
> I have yet to meet someone who's gotten used to git and then been happy about going back to subversion. ;-)
> Have you tried out one of git's graphical interfaces yet?
> John Ralls