On 27 Mar 2009 at 15:24, Dmitry Potapov wrote: > On Fri, Mar 27, 2009 at 10:21 AM, Ulrich Windl > <ulrich.windl@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > 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. > > To check out with the times stored in repository is a a bad idea, because it > will screw up 'make'. Hi, I don't understand: If I modify files, then do a make, then do check-in/check-out (and the file times are unchanged), how would that affect make? If I do an "update/merge from remote" (there is no total ordering of release numbers anyway) without a "make clean" before, I'm having a problem anyway. > > > > > 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. > > I am not sure what you want to achieve by having this number. Also, take > a look at "git describe", it may be close to what you want (or may be not). Basically I want to support my laziness: The system will increment some number and maybe change some text automatically that I'm to lazy to do. OK, there are still many commands I'll have to learn. Unfortunately some command names are not as "crispy" as they could be (i.e. you cannot easily find the right command name if you know what you are looking for, and if you have a command name, it's not very clear what it really does). That makes it hard for the beginners. Regards, Ulrich -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
