|
Rockbox mail archiveSubject: Re: svn propertiesRe: svn properties
From: Dominik Riebeling <dominik.riebeling_at_gmail.com>
Date: Sun, 13 Jun 2010 00:54:46 +0200 On Sat, Jun 12, 2010 at 11:15 PM, Marcin Bukat <marcin.bukat_at_gmail.com> wrote: > 2010/6/12 Frank Gevaerts <frank_at_gevaerts.be>: > It seems that properly set auto-props > in ~/.subversion/config will do the trick when speaking about properties > and git-svn. Interesting. If this works reliably it should definitely be on the GitVersionControl wiki page as a big fat notice. It might be a good idea to add a proposal for the auto-props section to that page as well. > The keywords thing is different matter. For me it is not very useful and I agree that the svn:keywords property isn't that useful. It's just another line of text that has to be assumed as completely wrong unless it can get checked against the repository, and if it can get checked against the repository there's no need for that line at all. However, if the current convention is to set it on all non-binary files then it should get set. A property I'm not sure about how to handle is svn:eol-style. I've seen some files having it set to native, and some files not having it set at all. Do we have a convention on this property? I'm not aware of any. The UsingSVN wiki page doesn't tell anything about this. Writing down the current convention on which properties to set (and to which values) should help cleaning up quite some confusion about keywords (I've seen people having manually edited the $Id$ line, so from my point of view keywords do cause at least some confusion). - Dominik Received on 2010-06-13 Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy |