Quoting Jonas Berlin on 09/05/2007 09:32 PM UTC: > Quoting Linus Torvalds on 09/04/2007 01:22 PM UTC: >> 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. I just realized that since git-cvsserver creates a SQLite database (assumably for keeping track of what cvs revision numbers map to which git commits) AND the "timezonized" timestamps are stored as strings in there, switching to UTC timestamps would either break current SQLite databases or then require backwards compatibility code to handle the pretty-printed timestamp (with the UTC unrolling code from the patch I sent). > 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 :) Another option would be to scrap support for old cvs clients.. I could investigate when the new format was introduced.. -- - 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
