Subversion 1.7 and 1.8

[Daniel J. Luke]

On Aug 19, 2013, at 7:42 AM, Jim Jagielski <jimjag at gmail.com> wrote:
> 
> It seems to me that this is *still* an issue... No further development upstream has been done to address this, afaict, so where does that leave us?
> 
> I repeat my offer to maintain subversion1.7

ok? so do it?

if you have commit, make the ports, commit them, and coordinate with the git-svn maintainer to have it depend on your new ports.

If you don't, make a ticket, attach patches, and then bug a committer (or the list) to get it committed.

... or work with upstream to get the bug fixed ...

--
Daniel J. Luke                                                                   
+========================================================+                        
| *---------------- dluke at geeklair.net ----------------* |                          
| *-------------- http://www.geeklair.net -------------* |                          
+========================================================+                        
|   Opinions expressed are mine and do not necessarily   |                          
|          reflect the opinions of my employer.          |                          
+========================================================+