Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
>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.
Try:
LESS=-inqMSFXx4
in your environment (or a suitable subset), it solves that problem.
>Overall I mostly miss more configurability: Ways to set default
>arguments to various commands,
Checkout "man git-config" (if you haven't already), and
"man gitattributes".
> better control over the blame line
>format. I also miss a counterpart to the -l option to cvs diff.
git diff .
(Note the trailing dot).
will limit the diff to the current directory and subdirs.
It's not quite the same as -l because it *does* recurse.
>> i believe there is something for eol handling in git, check the
>> hooks.
>They don't help for associating specific behaviors with specific
>files.
"man gitattributes", crlf attribute.
>> 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.
"man gitattributes", ident attribute.
>> > 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.
git-svn keeps a lot of state in memory, maybe even has memory leaks,
don't know for sure. What helps, everytime, is simply killing and
restarting git-svn. Git-svn is *very* good at restarting and picking up
right where it left off.
--
Sincerely,
Stephen R. van den Berg.
"People who think they know everything are annoying to those of us who do."
