Git config personalize

[cdelcol]

Added the ability to set personal values in .gitconfig via configure script.

./configure update

It helps eliminate rogue Jeff Heifetz commits everywhere :)

[jeffheifetz]

Do you still have those grunt scripts written, perhaps we should revive them for this.

[jeffheifetz]

Also it looks like this should be rebased now that the other pull was merged

[cdelcol]

I really didn't like this one...I did it late last night and it felt a bit dirty. The only other way I can think to re-use is to maintain a permanent branch and just keep rebasing from upstream.

I do have my old grunt version around but I really like the simplicity of yours :). Every time I went to use it I had to fix something first...kinda defeats the purpose. And an "interview" was on my to-do list for it but I never got to it.

Here are the general problems I had:

1. Obviously .gitconfig needs to change somehow. And once changed, it needs to be committed.
2. These are marked dirty as well: .iterm/.iterm, .vim/.vim. But I think this is because you committed the symlink...I haven't completely tracked it down.
3. This showed up as "untracked" last night while I was playing around: .vim/.netrwhist. I haven't looked into where it came from

Ultimately, cloning and owning may be the best approach after all :(. Unless we are in the mood for a complete plugin based approach to everything, and then you just clone and own a package manager file or something. It seems like alot of work for something that is used rarely...but I haven't found anything out there that does it. Maybe we could build and sell it for $19B.

[jeffheifetz]

Yeah maybe switching to the the grunt project scaffolding sounds best - http://gruntjs.com/project-scaffolding

I'm not sure whether .iterm/.iterm, .vim/.vim changes really matter but vim/.netrwhist definitely does not, its just a history file.

You're probably right about the clone and own approach, but for the current limitation of just git config how hard could it be.