From: Julian Phillips <julian@quantumfyre.co.uk>
To: Lucian Smith <lucianoelsmitho@gmail.com>
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 18:36:03 +0100 [thread overview]
Message-ID: <501dc45544c5582379df21a758d3be6c@quantumfyre.co.uk> (raw)
In-Reply-To: <CAHLmBr3Yn1tVhijmgRwd8hyxgasdc2VtfNi6pYP5FbEHjjb3Vw@mail.gmail.com>
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.
> 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.
Might be easier to just use Tortoise Git?
> -Lucian
>
> On Mon, Aug 22, 2016 at 10:54 PM, Eric Wong <e@80x24.org> wrote:
>> Alfred Perlstein <alfred@freebsd.org> wrote:
>>> I hadn't anticipated there be to translation between svn props and
>>> .gitattributes, it sounds a bit messy but possible, that said, is it
>>> not possible to commit .gitattribute files to the svn repo? Even in
>>> FreeBSD land such small token files are permitted.
>>
>> I'm not sure if an automatic translation is necessary or
>> desired (because of a corruption risk).
>>
>> Perhaps Lucian can clarify the situation for his repo.
>>
>>> As far as documenting svn-properties, most of the properties are
>>> used on the Subversion side either by subversion itself, or by
>>> scripts in the subversion repository. Perhaps a blurb "see the
>>> subversion documentation and/or your local subversion
>>> administrator's guide for properties and their uses." would suffice?
>>
>> Yes, perhaps with a workable example Lucian can use today with
>> any git v2.3.0 or later.
>>
>> Thanks for the quick response!
>>
>>> Opinions? Happy to look into it.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Julian
next prev parent reply other threads:[~2016-08-23 17:59 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 [this message]
2016-08-23 17:50 ` Lucian Smith
2016-08-23 19:07 ` Torsten Bögershausen
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=501dc45544c5582379df21a758d3be6c@quantumfyre.co.uk \
--to=julian@quantumfyre.co.uk \
--cc=alfred@freebsd.org \
--cc=e@80x24.org \
--cc=git-owner@vger.kernel.org \
--cc=git@vger.kernel.org \
--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).