Quoting Linus Torvalds on 09/04/2007 01:22 PM UTC: > So instead of turning it back into UTC here, I think git-cvsserver should > be changed to ask for the date in the native git format in the first > place. I agree. My first patch was a minimal-intrusion one to avoid unnecessarily breaking stuff. I guess at this point it's good to mention that current cvs implementations (at least 1.12.12) produce timestamps of format "yyyy-mm-dd HH:MM:SS +ZZZZ" (i.e. they do include timezone information) while older versions (at least 1.11.22) produce the UTC-only format "yyyy/mm/dd HH:MM:SS" which is currently used by git-cvsserver. Backwards compatibility generally being a good thing, while at the expense of timezone information, I chose to keep the older UTC-only format. Should you prefer to keep the timezone information, I'll update the cvs log format instead. Heck, I could even support both through some configuration option if you really wanted :) > That can be done various ways: > > - use the "raw log format" which has dates as seconds-since-UTC (and with > an *informational* timezone thing that should then just be ignored). > > This is likely the best approach, since anything but this will This seems straightforward to implement, so I will go with this. > For example, I think your patch may fix "cvs log", but I'm seeing some > suspiciously similar code in the "cvs annotate" handling, so I suspect > that would need it too. I will make sure this works as well. -- - xkr47 - 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
