On 5/15/11 12:26 PM, Bruce D'Arcus wrote:
> On Sun, May 15, 2011 at 12:15 PM, Dan Stillman<[email protected]>  wrote:
>> 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.
> I guess we can always play it by ear, but in any case leave the
> cs:updated value blank in the repo?

Yes, I think so.

>>>> 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.
> How do you determine the updated value: from the file itself, or from git?

We don't use the updated value—just the system timestamp when the script 
is run.

> For whatever reason, they're not (necessarily) the same thing.
>
> $ ls -l apa.csl
> -rw-r--r-- 1 bdarcus bdarcus 10186 2011-05-15 09:27 apa.csl
>
> $ git log --date=iso --pretty=format:"%ad" -1 apa.csl
> 2011-05-04 15:49:04 -0400

The first is just the checkout time, which git doesn't set specially.

The latter is the commit time.

We don't use either.

------------------------------------------------------------------------------
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

Reply via email to