On 5/15/11 2:23 PM, Carles Pina wrote:
> On 15 May 2011 19:04, Bruce D'Arcus<[email protected]>  wrote:
>> Carles,
>>
>> On Sun, May 15, 2011 at 1:52 PM, Carles Pina<[email protected]>  
>> wrote:
>>
>> ...
>>> I would not do it, I expect the cs:updated to have the timestamp in
>>> the repository, so it's easy to clone, users can just browse the
>>> repository using the github interface and download the ready-to-use
>>> style, etc.
>> Except that the github interface lists updated date-times for all
>> files by default already.
>>
>> And how do you respond to my previously noted problems? To repeat ...
>>
>> There are a variety of issues with forcing style authors to update the
>> cs:updated values manually:
>>
>> - it's tedious
>> - it's error prone (easy to forget to do, most basically)
>> - it mixes content and metadata (the metadata changes the sha1 value)
>>
>>> I would update the cs:updated when pushing with the pushing date, no?
>> You mean like pre-commit or pre-push script?
> yes, automatically. I should check which hook exactly (I don't see a 
> pre-push).
>
>> That solves some of my issues above, but not all of them.
> It only leaves the last issue, right? Can you elaborate a bit more? (I
> don't see the problem of changing the sha1 in the pre-commit hook, if
> you mean that this is the problem). Maybe a git specific problem?
> (I've never changed files during the pre-commit).

Well, it's what I said earlier: that the only way to do it (as far as I 
know, and it's the only way that really makes sense) is client side, and 
from what I gather of the page Bruce linked to [1], everybody who 
committed would need the script (and underlying interpreter) in question 
to be available on their system, since the only thing synced is the 
.gitattributes file.

[1] http://progit.org/book/ch7-2.html

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