Re: [microblaze-uclinux] [PATCH] microblaze: remove obsolete platforms

[Michal Simek <michal.simek@xxxxxxxxxxxxx>]

John Williams wrote:
> Hi Thomas,
> 
> Thanks for your comments.  It seems to be SVN->git conversion month -
> everyone is doing it, glibc just last week as well.
> 
> I agree generally with your comments - the issue we have to resolve
> before we can make such a move is actually an internal one - most of
> our commercial projects are performed on copies of the petalinux
> subtree, in a large SVN repository.  We are not ready to migrate all
> of our internal infrastructure to git, which would be required were
> petalinux also to make that move.
> 
> But, Michal for one is constantly hassling me to do the switch, so I
> can expect some change probably in the coming months.

:-) That's not hassle but recommendation.

Michal

> 
> Regards,
> 
> John
> 
> 
> On Fri, May 15, 2009 at 10:34 AM, Thomas Chou <thomas@xxxxxxxxxxxxx> wrote:
>> On 05/15/2009 01:08 AM, Nicolas Herve wrote:
>>> To avoid this, I am thinking in working in 2 parallel tree :
>>>
>>> - A fixed reference one that proves to work for my personal project (for
>>> me a pre-release v0.40rc1, alias SVN rev-5238, that should be equivalent
>>> to the uncleaned v0.40rc2, right ?)
>>> - and an ongoing svn release to keep the project, or project steps, in
>>> sync with development.
>>>
>> I think it will be much easier to work with git. I used "git-svn clone" and
>> "git-svn rebase" to convert the peta uclinux svn to git. I created local git
>> branches/tags to hold my projects. It is more useful than the centralized
>> svn
>> repository.
>>
>> Seeing that many other GNU projects switched fron svn to git, such as
>> busybox/
>> uClibc recently, maybe peta linux should think about it. A git repo takes
>> smaller
>> space and downloads faster.
>>
>> The nios2 uclinux distributes as git repo directly. All data is compressed
>> already
>> inside git repo. Users can create their own branches and pull update from
>> the server
>> when they want.
>>
>> The "broken after update" issue may still exist. But you can easily undo the
>> updates
>> on specific local git branches. And usually it won't take long for the
>> issues to be
>> fixed.
>>
>> Cheer,
>> Thomas
>>
>>
>>
>>
>>
>> ___________________________
>> microblaze-uclinux mailing list
>> microblaze-uclinux@xxxxxxxxxxxxxx
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>
>>
> 
> 
> 

-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/