Re: RCS keyword expansion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Schindelin:

The problem is this: for efficiency, git does not change files which have not changes between the last version checked out (whatever that is) and the current version.

This seems counterintuitive to people coming from SVN/CVS: they expect
_every_ file to be touched when checking out.

No? That would just be strange. Only the files that are actually changed should be updated, no others. A $Date$ or $Id$ will show the last time/commit that specific file was changed, not the latest global state (I guess the fact that most modern VCSs have global state makes this a bit more difficult to achieve, in RCS/CVS/PVCS and others the change history is local to a file and thus it is trivial to find the large change for that particular file).

As Randal already suggested: if you need something like this, you better have a build procedure which replaced $Date$ _at a given time_ (make install) with the current date.

But that's not what I want. Then my build procedure would need to do a "git status", or whatever you use to get the last commit information about a file, on each file that is changed and is to be installed. It would be a lot easier if that was done already on checkout through some kind of hook.

--
\\// Peter - http://www.softwolves.pp.se/
-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux