[Milkymist-devel] milkymist network driver bug

[Yann Sionneau]

Hi Daron,

How did you do your git mirror of the CVS ? Is there any tool to do that ?

Did you just cvs checkout and then git init . && git add * ?

You had to keep the CVS related files into your git, in order to be able 
to to cvs up, right ?

Can you explain to me how to do like you ?

Thanks :)

Regards,

Yann

Le 24/02/11 16:34, Daron Chabot a écrit :
> Hi Till,
>
> I'm not sure if Yann is doing the same, but I've been tracking the RTEMS
> cvs repos with git for some time and update it semi-regularly (doing an
> update now). I maintain one git repo that is a "mirror" of the cvs repo,
> and another git repo (clone of the mirror) for local development where I
> "rebase" my work on top of the cvs HEAD.
>
> You could do something similar, pulling Yann's branch(es) into your
> scratchpad repo...
>
> Just a thought.
>
>
> -- dc
>
> On Thu, Feb 24, 2011 at 10:17 AM, Till Straumann
> <strauman at slac.stanford.edu <mailto:strauman at slac.stanford.edu>> wrote:
>
>     On 02/24/2011 03:55 PM, Yann Sionneau wrote:
>
>         Le 24/02/11 14:40, Till Straumann a écrit :
>
>             On 02/24/2011 03:12 PM, Sebastien Bourdeauducq wrote:
>
>                 On Thu, 2011-02-24 at 11:13 +0000, Yann Sionneau wrote:
>
>                     Feel free to merge these commits with the CVS, but
>                     it will not be a
>                     straight forward merge since my github repository
>                     has a lot of commit
>                     that your CVS doesn't have. We are out of sync.
>
>
>                 Joel told me that the 4.11 release is not before a
>                 while. To reduce the
>                 administrative overhead, and unless someone sees this as an
>                 inconvenience, let's continue working on this BSP in the
>                 Git repository
>                 for now and I'll submit one big patch before the 4.11
>                 release.
>
>                 S.
>
>
>
>             Hmm - but I'd rather get only the BSP from your git repo
>             and work with the main-line RTEMS otherwise.
>
>             How can I do that?
>
>             Thanks
>
>
>         Well you can checkout my git repo, it's a clone of RTEMS CVS of
>         when I
>         started the GSoC back in the middle of 2010.
>
>
>     Well - that's not exactly what I want. I want to stay in-sync with
>     the current RTEMS development and use your latest BSP.
>
>
>     T.
>
>
>         Just check it out and you can play with RTEMS and the up-to-date
>         Milkymist BSP as if you were playing with RTEMS CVS :)
>
>         The qemu to use is a special one (with milkymist support) btw,
>         it's the
>         one from this git repo :
>         http://git.serverraum.org/?p=mw/qemu-lm32.git;a=summary
>
>         Link for how to compile lm32-qemu :
>         http://milkymist.org/wiki/index.php?title=Using_QEMU
>         Link for how to compile the BSP (but you sure know how to do
>         that better
>         than me :)) :
>         http://milkymist.org/wiki/index.php?title=RTEMS_build_instructions
>
>         Link on how to run some tests :
>         http://milkymist.org/wiki/index.php?title=Run_RTEMS_sample_applications_on_the_Milkymist_One_board_and_on_Qemu
>
>
>         And eventually if you want to try flickernoise (a GUI application) :
>         http://milkymist.org/wiki/index.php?title=Flickernoise_build_instructions
>
>         Have fun :)
>
>
>     _______________________________________________
>     rtems-users mailing list
>     rtems-users at rtems.org <mailto:rtems-users at rtems.org>
>     http://www.rtems.org/mailman/listinfo/rtems-users
>
>