On 5/15/11 12:05 PM, Bruce D'Arcus wrote: > On Sun, May 15, 2011 at 11:53 AM, Dan Stillman<[email protected]> wrote >> The problem with using smudge/clean filters in .gitattributes is that, >> as far as I can tell, they require particular client-side programs >> (e.g., Perl). A Windows user isn't going to have Perl. So leaving it >> blank seems best. > "Leaving it blank" but presumably using some other code outside of git > to create the proper cs:updated values?
Well that's what either filters or the styles page would do. > In any case, users aren't often going to interact with the git repos > directly, so not sure that's a reasonable argument against the git > filters? Who are "users" here? I was referring to style authors. If you think only a few people will be committing and checking out and we can require them to have Perl (or we'd be OK with the filters sometimes not being run), then filters are fine. Otherwise, this shouldn't happen via git, and it should be left to the styles page. >> None of the date logic on the styles page changed, by the way. The >> timestamps will be correct as the styles are updated. It's just more >> complicated to use the commit timestamp than to update the timestamp if >> the style has changed, and so I didn't bother. > Not following you here. Can you restate, in light of my questions above? The update script for the styles page assumes no filters and just replaces the contents of <updated/> with the current timestamp if the content of the file has changed since the last run. If we were using git filters it would just use <updated/> directly. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
