[
https://issues.apache.org/jira/browse/JCRVLT-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140350#comment-17140350
]
Julian Reschke edited comment on JCRVLT-398 at 6/19/20, 9:19 AM:
-----------------------------------------------------------------
> 3) I think using the approach from
> [https://help.github.com/en/github/using-git/configuring-git-to-handle-line-endings#per-repository-settings]
> is reasonable. Can you prepare a PR for that?
So I checked, and the checkout from git is the same as from svn trunk. And, it
also fails for the svn checkout. So the problem is not related to the switch to
Git. Opened separate ticket: https://issues.apache.org/jira/browse/JCRVLT-444
was (Author: reschke):
> 3) I think using the approach from
> [https://help.github.com/en/github/using-git/configuring-git-to-handle-line-endings#per-repository-settings]
> is reasonable. Can you prepare a PR for that?
So I checked, and the checkout from git is the same as from svn trunk. And, it
also fails for the svn checkout. So the problem is not related to the switch to
Git. Will open a separate ticket.
> Migrate Filevault to Git
> ------------------------
>
> Key: JCRVLT-398
> URL: https://issues.apache.org/jira/browse/JCRVLT-398
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Misc
> Affects Versions: 3.4.2, package-maven-plugin-1.0.4
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.4.6, package-maven-plugin-1.1.4
>
>
> As discussed in
> https://lists.apache.org/thread.html/8ea0d827d9e8488183648f2364ecd4e178b6d82e03193735aae6b5cd%40%3Coak-dev.jackrabbit.apache.org%3E
> we should migrate to Git.
> Good candidates are both repos for FileVault which should each get a
> dedicated Git repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
