> just out of curiosity which features are those for you? More subcommands to git-stash so that stashes actually get useful: Earlier the only option was to clear all of them or nothing, which means that one could only use them to very temporary things. Now I've got 12 stashes with assorted small hacks in them. For small things I think they're better than branches because you can give them longer descriptions and they don't clutter up the view in gitk.
There were some other odds and ends too which I don't quite remember. > (also what was the annoyance that caused you to get the git source to > fix it?) I haven't actually fixed anything yet. I pulled down the source to make me newer ubuntu packages. I took a look at fixing so that the pager isn't used for short output though; it's annoying that git status has started to use the pager too all the time. Overall I mostly miss more configurability: Ways to set default arguments to various commands, better control over the blame line format. I also miss a counterpart to the -l option to cvs diff. > i believe there is something for eol handling in git, check the > hooks. They don't help for associating specific behaviors with specific files. > there is an approximation for this, i believe it works by adding the id > at checkout, and removing it at checkin. again, see the hooks Ok. That'd be nice to have by default. Would require properties or something like them, though. > > Btw, git-svn choked on the pike svn repo. > > hmm, i think i managed to get through it ayear ago. did you access the repo > locally? i set up a copy of the repo on my machine to do the import. No, over the net. Do you think the network traffic increases with each imported commit? That'd be even worse. My theory is that git-svn doesn't use a good indexed storage to map between hashes and svn revisions, or something like that.
