From: Petr Baudis Date: Tue, 10 May 2005 00:32:35 GMT Subject: Re: [RFC] Renaming environment variables. Message-ID: <20050510003235.GK15712@pasky.ji.cz> In-Reply-To: <20050509201520.GL24216@cip.informatik.uni-erlangen.de> Dear diary, on Mon, May 09, 2005 at 10:15:20PM CEST, I got a letter where Thomas Glanzmann told me that... > > Here is a patch, requesting for comments. > > sounds good. But I would forget about downward compatibility. There is > no need to maintain it at this early stage. Sure there is. We are actually far from an early stage now, I'd say. And what I don't want to see are commits with messed up author information since people upgraded and did not notice. > And one thing which bothers me all the time but never spoke up about it: > There is no way to provide a GIT_COMMIT_DATE. This would be useful for > vendortracking a CVS repository for example. You could use GIT_AUTHOR_DATE. :-) But yes, I actually agree. When you are doing vendortracking of CVS repository, you have one canonical source of the commit, and when you do the CVS import twice independently, I think you _want_ the same commit, since it _is_ the same commit after all (if the history is same too, obviously). -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor