On Tue, Aug 23, 2016 at 10:36 AM, Julian Phillips <julian@xxxxxxxxxxxxxxxxx> wrote: > On 23/08/2016 17:14, Lucian Smith wrote: >> >> Thanks for the quick responses! >> >> My situation is that the git side is entirely whatever github.org is >> running; presumably the latest stable version? They provide a URL for >> repositories hosted there that can be accessed by an SVN >> client--somewhere on github is the 'git-svn bridge' (as I understand >> it): something that receives SVN requests, translates them to >> git-speak, and replies with what SVN expects. > > > The ability to use a Subversion client is functionality provided by GitHub, > and not native to git itself. So unless someone for the appropriate GitHub > team happens to read this thread I expect there isn't much we can do to > help. I don't know if they've even provided any real detail of how they > implemented the bridge. All right, that makes sense. And yeah, it was hard to find any information about the bridge, which is why I ended up here... >> There is indeed a .gitattributes file in the repository, but the SVN >> client doesn't know what to do with it. My hope was that something in >> the bridge code, that translated SVN requests to git and back, could >> take the SVN request, "Please give me this file; I'm on Windows" look >> at the .gitattributes file in the repository, and hand out a file with >> CR/LF's in it. Conversely, when SVN tells git "Here is the new >> version of the file to check in," the bridge could look at the file, >> realize it had CR/LF's in it, look at the .gitattributes file to know >> if it needed to be converted, and then convert it appropriately. >> >> I can imagine a full-blown bridge that could even translate the SVN >> EOL propset back and forth appropriately, but I'm not sure if going >> that far is necessary and/or helpful. >> >> I don't know if this is the right mailing list for that particular bit >> of software, but it at least seemed like a good place to start. Thank >> you! > > > Supported properties are listed here: > https://help.github.com/articles/subversion-properties-supported-by-github/ > > You'll need to ask GitHub to implement support for the svn:eol-style > property I expect. Thanks for finding that! That even has an 'ask a human' button, which I expect is my next step. > Might be easier to just use Tortoise Git? It may be! But thanks for the responses anyway. -Lucian -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html