Re: Re: Git migration & revcheck tag
| From: | Alexey Shein | Date: | Tue, 27 Mar 2012 06:50:10 +0000 |
| Subject: | Re: Re: Git migration & revcheck tag | ||
| References: | 1 2 3 4 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969383740@lists.php.net to get a copy of this message | ||
27 марта 2012 г. 8:05 пользователь Daniel Convissor
<danielc@analysisandsolutions.com> написал:
> Hola:
>
> On Sat, Mar 03, 2012 at 07:15:45PM -0500, Daniel Convissor wrote:
>> Hi Folks:
>>
>> > > About Git migration : how are we deal with the revcheck tag ?
>> >
>> > I don't know much about it, but git supports keywords. You can have an
>> > $Id$ field that is replaced by the sha1.
>>
>> I think the best we can do is a date keyword tag. They're discussed at
>> http://progit.org/book/ch7-2.html
>
> I'm following up on the email I sent earlier this month. I didn't see
> any responses. Wondering what people think of the idea.
I think it can work. We need to implement those filters in php (since
it's the basic requirement of building docs anyway) and keep them in
doc-base/, because as stated in ProGit link you posted,
".gitattributes are kept into repository but filters are not":
> You can see how powerful this technique can be for customized applications. You have to be
> careful, though, because the .gitattributes file is committed and passed around with the project but
> the driver (in this case, dater) isn’t; so, it won’t work everywhere. When you design these
> filters, they should be able to fail gracefully and have the project still work properly.
Isn't $Date$ keyword is dependent from commiter's timezone? That would
be a pain to maintain. Although we should be careful when replacing
$Date: <some date here> back not to spoil any php code examples.
--
Regards,
Shein Alexey