From: "Torsten Bögershausen" <tboegi@web.de>
To: Lucian Smith <lucianoelsmitho@gmail.com>,
Julian Phillips <julian@quantumfyre.co.uk>
Cc: Eric Wong <e@80x24.org>, Alfred Perlstein <alfred@freebsd.org>,
git@vger.kernel.org, git-owner@vger.kernel.org
Subject: Re: git-svn bridge and line endings
Date: Tue, 23 Aug 2016 21:07:33 +0200 [thread overview]
Message-ID: <cfb712ee-ff0e-0f62-0477-6edf483d4101@web.de> (raw)
In-Reply-To: <CAHLmBr1Cd_JimZEsLUjG=+v4CgsXGGzkyFizZ1U5YSSMqjsEvw@mail.gmail.com>
On 23.08.16 19:50, Lucian Smith wrote:
> On Tue, Aug 23, 2016 at 10:36 AM, Julian Phillips
> <julian@quantumfyre.co.uk> 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.
Most text-files have been commited with LF:
/tmp/ttt/sbml-test-suite> git ls-files --eol | grep "i/lf" | wc -l
10266
Some have been commited with CRLF:
/tmp/ttt/sbml-test-suite> git ls-files --eol | grep "i/crlf" | wc -l
1620
The whole repo deserves to be normalized and equipped with a .gitattributes file,
see
https://www.kernel.org/pub/software/scm/git/docs/gitattributes.html
next prev parent reply other threads:[~2016-08-23 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHLmBr2CRzt58RB+_YmnXcyost-R5=Ff51tALf1xh0kGk+frDw@mail.gmail.com>
2016-08-23 0:04 ` git-svn bridge and line endings Lucian Smith
2016-08-23 3:07 ` Eric Wong
2016-08-23 4:58 ` Alfred Perlstein
2016-08-23 5:54 ` Eric Wong
2016-08-23 16:14 ` Lucian Smith
2016-08-23 17:36 ` Julian Phillips
2016-08-23 17:50 ` Lucian Smith
2016-08-23 19:07 ` Torsten Bögershausen [this message]
2016-08-23 16:43 ` Torsten Bögershausen
2016-08-23 17:08 ` Lucian Smith
2016-08-23 17:26 ` Junio C Hamano
2016-08-23 17:31 ` Lucian Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfb712ee-ff0e-0f62-0477-6edf483d4101@web.de \
--to=tboegi@web.de \
--cc=alfred@freebsd.org \
--cc=e@80x24.org \
--cc=git-owner@vger.kernel.org \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=lucianoelsmitho@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).