How do I regularly clean up .git/objects/pack/tmp_* files?

2017-06-03 Thread Dun Peal
Hi there, I try to follow the best practice of regular repo maintenance, which afaik consists of running `git gc` every week or so. So I thought I had a well-maintained repository, and was quite surprised to discover some very large .git/objects/pack/tmp_* files, which apparently are entirely nee

Re: trustExitCode doesn't apply to vimdiff mergetool

2016-11-27 Thread Dun Peal
developers change this default, or at least let us override it for the builtin invocations. Finally, if you're not using mergetools, how do you resolve conflicts? On Sun, Nov 27, 2016 at 12:08 AM, Jeff King wrote: > On Sat, Nov 26, 2016 at 09:44:36PM -0500, Dun Peal wrote: > >&

trustExitCode doesn't apply to vimdiff mergetool

2016-11-26 Thread Dun Peal
I'm using vimdiff as my mergetool, and have the following lines in ~/.gitconfig: [merge] tool = vimdiff [mergetool "vimdiff"] trustExitCode = true My understanding from the docs is that this sets mergetool.vimdiff.trustExitCode to true, thereby concluding that a merge hasn't been success

Re: $GIT_DIR/info/exclude fails to negate a pattern defined by core.excludesfile

2014-10-13 Thread Dun Peal
it does work as expected. Thanks, D. On Sun, Oct 12, 2014 at 7:53 PM, Duy Nguyen wrote: > On Sun, Oct 12, 2014 at 9:58 AM, Dun Peal wrote: >> I have the pattern `*.out` defined in my `core.excludesfile`. >> According to the documentation[1], patterns defined in >> `$GIT_DI

Re: $GIT_DIR/info/exclude fails to negate a pattern defined by core.excludesfile

2014-10-12 Thread Dun Peal
likely to want to override global exclusions for a specific project, than override specific project settings with a global exclusion file (that last one really makes no sense imho). Thoughts? On Sat, Oct 11, 2014 at 10:58 PM, Dun Peal wrote: > I have the pattern `*.out` defined in my `core

$GIT_DIR/info/exclude fails to negate a pattern defined by core.excludesfile

2014-10-11 Thread Dun Peal
I have the pattern `*.out` defined in my `core.excludesfile`. According to the documentation[1], patterns defined in `$GIT_DIR/info/exclude` take precedence over `core.excludesfile`, so for one particular project that needs to track some `.out` files, I created `$GIT_DIR/info/exclude` with just one

"warning: There are too many unreachable loose objects; run 'git prune' to remove them."

2012-08-29 Thread Dun Peal
Hi, I am getting this error every time I pull. All the following have been executed, but failed to remove this warning: git prune git prune --expire now git gc git gc --aggressive What should I do? Thanks, D. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a mes