Hi Gary,
   I'm wondering if you'd like the idea that, shall we revert to and retain
Xalan's source repository to SVN? GitBox is not mandatory as of now for use
by Apache projects. For retaining SVN for Xalan, I guess you'd need to
discard effort spent until now for trying moving Xalan to GitBox, and that
may sound little annoying to you I guess.

Xerces is on SVN, and I believe Xerces is closely related to Xalan. I
think, as of now Xerces has no plans (I've not seen any discussion about
this on Xerces lists, other than one email from you on one of Xerces's list
few weeks ago suggesting Xerces's move to GitBox) to moving to GitBox.

If you're certain to move Xalan to GitBox, then its fine. I'm with you for
that, and I believe that others would also have no objections.

I'm also curious to know that, GitBox other than an alternative to SVN at
Apache, what would be GitBox's other advantages for Xalan? I can see that,
moving Xalan to GitBox would allow Xalan community to use GitHub (which is
hugely popular) as well, as a source repository.

On Tue, Apr 16, 2019 at 8:02 PM Gary Gregory <[email protected]> wrote:

> This failed last night:
>
> ggregory@ggregory-VirtualBox:~/share/xalan-c$ svn2git
> https://svn.apache.org/repos/asf --username ggregory --authors
> ./authors.txt --verbose --trunk /xalan/c/trunk --branches /xalan/c/branches
> --tags /xalan/c/tags
> Running command: git svn init --prefix=svn/ --username='ggregory'
> --no-metadata --trunk='/xalan/c/trunk' --tags='/xalan/c/tags'
> --branches='/xalan/c/branches' https://svn.apache.org/repos/asf
> Running command: git config --local --get user.name
> Running command: git config --local svn.authorsfile ./authors.txt
> Running command: git svn fetch
> Author: (no author) not defined in ./authors.txt file
>
> command failed:
> git svn fetch
>
> Any thoughts?
>
> Yes, I have authors.txt in the current folder and it has the same content
> I used to convert https://svn.apache.org/repos/asf/xalan/pmc successfully.
>
> Thank you,
> Gary
>




-- 
Regards,
Mukul Gandhi

Reply via email to