From: Shawn Pearce <spearce@spearce.org>
Date: Fri, 02 Jun 2006 02:35:45 GMT
Subject: Re: What's in git.git (part #2)
Message-ID: <20060602023545.GA5039@spearce.org>
In-Reply-To: <7v64jli66m.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:
>  - reflog from Shawn.  Do people find this useful?  I've enabled
>    reflog on "next" branch in my development repository to see
>    how useful it would be for myself a few days ago, and also in
>    a linux-2.6 repository I use for testing (I do not hack on
>    kernel myself).  

I find it useful to track what I've sent to you just in case I
screw up some ref somewhere.  I like knowing that if I perform a
bad update-ref call (which I'm prone to do sometimes) that I can
recover quickly as the log exists.

Not having that prior ref value was about the only area of `possible
data loss' that I've every really noticed with GIT.  Well, that and
only having one repository holding all of your important files and
you rm -rf the dang directory by accident one day...  but that's
just foolishness on the user's part.  :-)

>  - using ~/.gitrc to give a fall-back default when
>    $GIT_DIR/config does not have values.
> 
>  - command aliases and possibly default arguments via the
>    configuration file.

I'm certainly interested in these two - and I don't think I'm alone
when I say that.  :-)

-- 
Shawn.