Re: On git 1.6 (novice's opinion)

From: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>
Date: Mar 27, 2009, 09:50 UTC
Message-ID: <49CCAF5D.21814.24B4DE63@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
In-Reply-To: <20090327090554.5d6160f2@pc09.procura.nl>

On 27 Mar 2009 at 9:05, H.Merijn Brand wrote:

Show 18 quoted lines

> On Fri, 27 Mar 2009 08:21:36 +0100, "Ulrich Windl"
> <ulrich.windl@rz.uni-regensburg.de> wrote:
> 
> > What I'd like to see in git (My apologies if some were already discussed to 
> > death):
> > 
> > 1) The ability to use the file's time at the time of add/commit instead of
> >    the current time, and the ability tho check outfiles with the times stored
> >    in the repository.
> > 
> > 2) Keyword substitution. I know it's controverse (dealing with binary files),
> >    but I'd like to have some automatic version numbering keyword at least:
> >    Initial idea is that every commit with a change increments the number by
> >    one, and when merging numbers a and b, the resulting number is max(a, b) + 1.
> 
> impossible. Even with checkin- and checkout hooks, you won't get that
> SCCS behaviour. They have to be better in something too :)
> /me still misses that but got used to it

Hi,

what made me wonder is this (about item 1): I thought I've read that blobs store content and attributes, so very obviously I wondered why not store thr "right attributes" (i.e. the time of the file). My reasoning: You make some changes, then test them (which might last several hours or days). The if I'm happy I'll "commit". Naturally I want to see the time of change for each file when the change had been actually made, not when the change was committed. Likewise when checking out, I want to be able to see the time of modification, not the time of commit. I'm aware that many people don't care about such differences...

> 
> > 3) "git undo": If possible undo the effects of the last command.

If impossible, add confirmations for some "dangerous" (non-obvious) commands before doing possibly harmful things. Maybe adding a kind of "user-level setting" (novice, expert, guro) could control such confirmations.

Show 9 quoted lines

> > 
> > Following are some random remarks from a first-time git user, regarding the 
> > buld/install:
> > 
> > Notes on building git-1.6.1.3 on openSUSE 11.0:
> > There is no "asciidoc"; the INSTALL should be more verbose on special
> > requirements (i.e. additional packages needed, and where to get them).
> 
> # zypper in asciidoc libcurl-devel

"asciidoc" doesn't seem a popular package on some distributions; mine lacks it...

> 
> (yes, 'make install-man' should stop soon after detecting asciidoc is
> not installed

Regards, Ulrich