You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Omer Faruk Sen <om...@gmail.com> on 2010/06/09 10:51:16 UTC
subversion binary file keyword expansion
Hi,
As far as I know binary files are not processed in keyword expansion
For example I have a binary contains $Revision$
svn add mybinary
svn propset svn:executable ON mybinary (just in case)
svn commit
After commit md5 of the binary changes. Is that normal behaviour. I
use subversion-1.6.2
Regards.
Re: subversion binary file keyword expansion
Posted by Piotr Kabacinski <pi...@kabot.net>.
On 09-06-2010 12:51, Omer Faruk Sen wrote:
> As far as I know binary files are not processed in keyword expansion
> For example I have a binary contains $Revision$
>
> svn add mybinary
> svn propset svn:executable ON mybinary (just in case)
> svn commit
>
> After commit md5 of the binary changes. Is that normal behaviour. I
> use subversion-1.6.2
Try to use svn:mime-type application/octet-stream instead.
--
Piotr Kabacinski
a2Fib3Q=========
Re: subversion binary file keyword expansion
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Omer Faruk Sen wrote on Wed, 9 Jun 2010 at 13:51 -0000:
> Hi,
>
> As far as I know binary files are not processed in keyword expansion
> For example I have a binary contains $Revision$
>
> svn add mybinary
Please post the output of the above command, and of 'svn proplist -v mybinary'.
(you can run proplist before you commit)
> svn propset svn:executable ON mybinary (just in case)
Irrelevant. (think shell scripts)
> svn commit
>
Do you have any ~/.subversion/config[auto-props] entries matching 'mybinary'?
> After commit md5 of the binary changes. Is that normal behaviour. I
> use subversion-1.6.2
>
> Regards.
>
>
Re: subversion binary file keyword expansion
Posted by Omer Faruk Sen <om...@gmail.com>.
Yes exactly my point is that but it seems it doesn't work that way
On Wed, Jun 9, 2010 at 3:02 PM, Andy Levy <an...@gmail.com> wrote:
> On Wed, Jun 9, 2010 at 06:51, Omer Faruk Sen <om...@gmail.com> wrote:
>> Hi,
>>
>> As far as I know binary files are not processed in keyword expansion
>> For example I have a binary contains $Revision$
>>
>> svn add mybinary
>> svn propset svn:executable ON mybinary (just in case)
>> svn commit
>>
>> After commit md5 of the binary changes. Is that normal behaviour. I
>> use subversion-1.6.2
>
> Keyword expansion should only happen on files with svn:keywords set.
>
Re: subversion binary file keyword expansion
Posted by Piotr Kabacinski <pi...@kabot.net>.
On 09-06-2010 14:02, Andy Levy wrote:
>> As far as I know binary files are not processed in keyword expansion
>> For example I have a binary contains $Revision$
>>
>> svn add mybinary
>> svn propset svn:executable ON mybinary (just in case)
>> svn commit
>>
>> After commit md5 of the binary changes. Is that normal behaviour. I
>> use subversion-1.6.2
>
> Keyword expansion should only happen on files with svn:keywords set.
Yes, but as you said md5 changed. This change is caused by keyword
substitution or by changing EOL?
--
Piotr Kabacinski
a2Fib3Q=========
Re: subversion binary file keyword expansion
Posted by Andy Levy <an...@gmail.com>.
On Wed, Jun 9, 2010 at 06:51, Omer Faruk Sen <om...@gmail.com> wrote:
> Hi,
>
> As far as I know binary files are not processed in keyword expansion
> For example I have a binary contains $Revision$
>
> svn add mybinary
> svn propset svn:executable ON mybinary (just in case)
> svn commit
>
> After commit md5 of the binary changes. Is that normal behaviour. I
> use subversion-1.6.2
Keyword expansion should only happen on files with svn:keywords set.