[jsword-devel] Git

[Trenton D. Adams]

Oh, almost forgot, git svn also takes --ignore-paths option, which I 
believe prevents tracking the history of files you don't want in the new 
repo, such as jars or other non-desirable binary files.

On 12-03-29 01:14 PM, Trenton D. Adams wrote:
> Git automatically takes svn layouts, and changes them to fit git. I
> don't recall exactly how I did it, but I believe it was "git svn clone"
> with the --stdlayout option, and use the base repo (not trunk).
>
> I'm sure some googling would help But, it wouldn't take long to setup a
> test repo with a few files, some tags, some branches, and then try it on
> your local machine.
>
> On 12-03-29 09:35 AM, DM Smith wrote:
>> On 03/29/2012 10:55 AM, Martin Denham wrote:
>>> I wonder what would happen if you just asked github to import the
>>> current svn repository. They say they have no hard limits on storage.
>>
>> It should work just fine. I think that is what Matěj has done for
>> another git server.
>>
>> But there are two things regarding such an import.
>> 1) The layout follows that of SVN rather than GIT. For example, you'd
>> have trunk rather than master and the tags would be branches rather than
>> GIT tags. Not a big deal for either but it is easy to cleanup.
>>
>> 2) The size of the checkout will be large due to the jars and other
>> binaries. We can remove them, but it really needs to be done before
>> anyone uses it to do work. I've had a few translators object to the
>> checkout size in SVN just to get the resources to translate. By removing
>> these artifacts and suggesting --depth, their problem might be solved.
>>
>> Right now, I'm trying to get the build to work without them in source
>> code control. (Thus the ivy work for JS-104).
>>
>>>
>>> Martin
>>>
>>> On 28 March 2012 01:41, Trenton D. Adams <trent at trentonadams.ca
>>> <mailto:trent at trentonadams.ca>> wrote:
>>>
>>> On 12-03-27 02:53 AM, Matěj Cepl wrote:
>>>
>>> On 27.3.2012 03:44, Trenton D. Adams wrote:
>>>
>>> Git has the option of only cloning the most recent
>>> history. Use the
>>> --depth option.
>>>
>>>
>>> That's good for random Joe Developer, but we are here talking
>>> about the
>>> canonical repository of the project.
>>>
>>> Matěj
>>>
>>>
>>> I didn't say you shouldn't do the cleanup! :D But, even if you do
>>> clean it up, it's still going to be quite large. That's just the
>>> nature of git.
>>>
>>>
>>> _______________________________________________
>>> jsword-devel mailing list
>>> jsword-devel at crosswire.org <mailto:jsword-devel at crosswire.org>
>>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jsword-devel mailing list
>>> jsword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>
>>
>>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel