From: Eric Wong <e@80x24.org>
To: Alfred Perlstein <alfred@freebsd.org>
Cc: Lucian Smith <lucianoelsmitho@gmail.com>, git@vger.kernel.org
Subject: Re: git-svn bridge and line endings
Date: Tue, 23 Aug 2016 05:54:18 +0000 [thread overview]
Message-ID: <20160823055418.GA5990@whir> (raw)
In-Reply-To: <5e17164f-f669-70c2-de78-25287ab59759@freebsd.org>
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.
next prev parent reply other threads:[~2016-08-23 5:54 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 [this message]
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
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=20160823055418.GA5990@whir \
--to=e@80x24.org \
--cc=alfred@freebsd.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).