Re: Problems with filters and git status - reproduction steps

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

 



Michael J Gruber:

I get "Changed but not updated" already here!

With git 1.5.6.5, I do get that. With git 1.6.4, I seem to only get it after the last step.

I have 1.5.6.5 on the server with the master repo, and am running 1.6.4 on the client (although when I ran the recipe through a shell script, I got the unclean status earlier, which made me think it ran an earlier version I have installed in another directory).

Do you really want the date in the checked-in version of the file?

Yes. This way, the checked out copy that makes my web server can do its job without requiring any of the filters being installed. And the files in history are marked as necessary.

I would assume otherwise. Then your clean filter should really be the smudge filter, and you would need a clean filter to go with it (remove the date and restore the keyword).

The problem with that approach is that the "smudge" filter does not have access to the file name, and so can not look up the last change date of the file it is re-writing. And I want the last time the file was *changed*, not the time it was checked out.

Also, I imported my entire CVS history with keywords expanded to allow for this (and "checked out" the Git-generated tree over my CVS check-out to not have Git update all the time-stamps).

--
\\// 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]