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

A fix for issue 3471

From: Rick Varney <rick.varney_at_sbcglobal.net>
Date: Mon, 21 Feb 2011 21:54:12 -0800 (PST)

Hello, I am introducing Subversion into our development environment.  We are using a lock-modify-unlock stategy for all of our files.  I do not claim this is the best or most efficient way to use Subversion, but it best fits the mindset of the developers at my particular site.  We have installsed Subversion 1.6.6. We ran into the bug documented as issue 3471: "svn up touches file w/ lock & svn:keywords property" http://subversion.tigris.org/issues/show_bug.cgi?id=3471   This is an annoyance for us, as we are using make to do our builds.   I am new to the subversion community, though I have had my eye on it for a long time.  Here are my questions:   1.  Is there a way for me to find out if there is planned fix for this issue? 2.  If there is not a plan to fix this issue in an upcoming release, is there a way I can find out if anyone else has submitted a fix? 3.  If there there is no submitted fix, how would I go about submitting one should I attempt a fix myself? 4.  If I were to attempt a fix, I would likely not be able to spend a great deal of time fully verifying it, given that this is outside of my usual job responsibilities.  Is there a way to submit a fix that others could help verify - assuming that there are benevolent souls in the community that do this sort of thing?   In short, please clue me in on the conventions of getting or making a fix to a bug I care about.  I am fine if the answer is "Read The Fine Manual", but do please point me right manuals.   Many thanks in advance!   Best regards,   Rick Varney
Received on 2011-02-22 08:59:58 CET

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.