On Fri, Feb 6, 2009 at 10:12 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > Using update time does ensure that it is monotonical, and it > wouldn't ever be earlier than the time repository started to be > available, but it changes from clone to clone. I don't think it changing from clone to clone is a problem. Monotony and the ability to properly catch when the underlying data really changed are much more important factors. After all, there is no _requirement_ that Last-Modified be used for If-modified-since headers (although it is recommented, and clients that don't follow the recommendation are warned to be aware of all possible odd problems arising from not using it). The real question is: _how_ do you get the (branch) update time? -- Giuseppe "Oblomov" Bilotta -- 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
