[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

AW: Re: Standardize on ASCII type: dos2unix pre-commit hook?

From: Felix Gilcher <gilcher_at_exozet.com>
Date: 2006-03-16 10:30:18 CET


voting for the bug might make you feel better but will not change the priority of the bug. The developers have stated multiple times that they pay no attention to the number of votes for a bug (the reasons are all on the list, so I won't reiterate all of them).
However, if you wish this feature to be implemented, there are a couple of things you can do:

 - write the patch (just as you mentioned).
 - if you lack the time or the skills (like me), you can still write a formal design proposal of how this feature should exactly work, so that it may be discussed on the dev list - it seems to me that this has not happended yet. Features/enhancements that have a design proposal that is generally accepted seem to get implemented faster.
 - pay someone to do it for you, perhaps in cooperation with some of the other people that would like to see this feature implemented.



Daniel Serodio <mailto:daniel.listas@xxx.com.br> schrieb am Mittwoch, 15. März 2006 18:34:

> Then let's vote for (or better yet, implement) this bug!
> http://subversion.tigris.org/issues/show_bug.cgi?id=1974
> HTH,
> Daniel Serodio
> Res Pons wrote:
>> I hope soon there's a server side control feature for this. Setting
>> auto props per user just doesn't make any sense to me and if user set
>> their own, wouldn't there be a conflict? I tried to implement this
>> feature on my server and I was told it yet doesn't exist or not
>> possible.
>> ----Original Message Follows----
>> From: Matt England <mengland@mengland.net>
>> Subject: RE: Standardize on ASCII type: dos2unix pre-commit hook?
>> Does there exist a way to manage this mechanism (svn:eol-style
>> property, or anything else) such that "ASCII standarizations" will be
>> made regardless of client-side settings?
>> In other words, is this a client-side setting or a server-side
>> setting? Or is this question pertinent?
>> If it's a client-side setting, then it's not nearly as useful to me.
>> This goes back to the general issue I have with subversion where I
>> can't manage the properties of clients from a single point (namely
>> the server), which would be much more powerful, in my opinion. Is
>> there any move afoot for future subversion changes to support a
>> single-point-of-client control?
>> -Matt
>> At 3/12/2006 07:04 PM, Tony Morris wrote:
>>> I am by no means an expert, but I have used the svn:eol-style
>>> property. You can set it to apply to commits of specific file types
>>> in the Subversion config file as an 'auto-prop'.
>>> Tony Morris
>>> http://tmorris.net/
>>> -----Original Message-----
>>> From: Matt England [mailto:mengland@mengland.net]
>>> Sent: Monday, March 13, 2006 10:52 AM
>>> To: SVN Users email list
>>> Cc: mengland@mengland.net
>>> Subject: Standardize on ASCII type: dos2unix pre-commit hook?
>>> The various repos I administer finds users putting different
>>> text/ASCII types (dos and unix, maybe some old mac) in the
>>> text-file content. This screws up the diff comparisons, merges,
>>> and other things.
>>> I'd like to auto-force a standard unix text across certain repos
>>> (if not all of them). My current thinking is to run a
>>> dos2unix/mac2unix pre-commit hook. Is this a good/best way to go?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

Felix Gilcher
Head of IT Development
Exozet Berlin GmbH
Rotherstraße 20
10245 Berlin
eMail: gilcher@exozet.com
URL: www.exozet.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 16 10:31:45 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.