+1 for doing it the next 4.0 release. If, when you do it, this change is the only change in the commit, you'll still be able to isolate any other commit (affecting behavior) and view it with a clean diff.
Things will only get cloudy if you try to diff commits spanning a period that includes this change. It's a modest "downside" I suppose, but it won't be substantively less of a downside if you wait for 4.1 IMHO. drew Sent from my ASUS Eee Pad Eric Dalquist <[email protected]> wrote: >I'm for this as well. I'll create a jira issue and schedule it to remove >all the keywords. > >I was thinking 4.1 since it will this will touch all files and affect >diffs but I'm thinking that people already have pain with diffs so doing >this for the next 4.0 release might not be any more disruptive than the >keywords already are. Thoughts on when we should do this? > >-Eric > >On 04/10/2012 11:06 AM, Cris J Holdorph wrote: >> I'm dealing with this every day in another project and it drives me >> bonkers. I vote not just for the $Revision$ keyword removal, but for >> ALL svn keywords to be removed. They are an annoyance when trying to >> diff. >> >> +1 even if this is limited to just the $Revision$ keyword. >> >> ---- Cris J H >> >> On 04/10/2012 08:40 AM, Eric Dalquist wrote: >>> After dealing with this in 'yet another diff' the $Revision$ CVS/SVN >>> keyword is on my hit list. Anyone have any objections to doing a mass >>> delete of that line in all files for 4.1? >>> >>> -Eric >>> >>> >> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
