Re: [Openocd-development] Moving to git

2009-10-08 Thread Nicolas Pitre
On Wed, 7 Oct 2009, Raúl Sánchez Siles wrote: I said I didn't want to start a flamewar and provided there has been, at least, a slight interest on my messages, I'll try to clear up some point and leave the thread alone. I cannot resist correcting you on one point though. [...] That

Re: [Openocd-development] Moving to git

2009-10-07 Thread Øyvind Harboe
W.r.t. choice of version control, many OpenOCD maintainers have extensive git expertise and nobody has expressed interest in Mercurial. Lots of patches come from git at this point so many top contributors clearly use it too. You'd be hard pressed to get any sort of enthusiasm about any other

Re: [Openocd-development] Moving to git

2009-10-07 Thread Øyvind Harboe
Try now. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] Moving to git

2009-10-06 Thread Ronald Vanschoren
!!! And if anyone objects to GIT, please speak up ASAP !!! Why are we moving to GIT anyway? What was wrong with SVN? gr. Ronald ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] Moving to git

2009-10-06 Thread Ronald Vanschoren
I did not but I have now and tbh I'm not impressed. Sure git has some advantages, but do we really care about the distributed nature, better branch support, higher performance and other things? What I read was: Also not mentioned are Subversion's support for http(s) and WebDAV, and its

Re: [Openocd-development] Moving to git

2009-10-06 Thread Nico Coesel
1. Berlios svn will be made read only and the svn head will be deleted, leaving behind only a README w/reference to the openocd project at sourceforge. The entire svn history will remain available on Berlios indefinitely. Question from a dumb-ass: Is the entire repository (including all

Re: [Openocd-development] Moving to git

2009-10-06 Thread David Brownell
On Monday 05 October 2009, Ronald Vanschoren wrote: Please keep in mind some people are  using Windows here. There are quite a few folk using git from Windows... Not three hours ago I pulled a repository onto an XP machine (via cygwin). The build breakage was completely unrelated to GIT.

Re: [Openocd-development] Moving to git

2009-10-06 Thread David Brownell
On Monday 05 October 2009, Nico Coesel wrote: Is the entire repository (including all branches and tags) moved to SF or just head? Right now there are git-svn repositories that have whatever could be imported, but I think just the trunk is at SF. Is there anything in those branches/etc that's

Re: [Openocd-development] Moving to git

2009-10-06 Thread Øyvind Harboe
On Tue, Oct 6, 2009 at 8:45 AM, Nico Coesel ncoe...@dealogic.nl wrote: 1. Berlios svn will be made read only and the svn head will be deleted, leaving behind only a README w/reference to the openocd project at sourceforge. The entire svn history will remain available on Berlios indefinitely.

Re: [Openocd-development] Moving to git

2009-10-06 Thread Raúl Sánchez Siles
El Lunes, 5 de Octubre de 2009 22:07:35 David Brownell escribió: On Monday 05 October 2009, Øyvind Harboe wrote: In short, the following will happen: 1. The source will be held in git. https://sourceforge.net/projects/openocd/ !!! And if anyone objects to GIT, please speak up ASAP

Re: [Openocd-development] Moving to git

2009-10-06 Thread Grant Edwards
On 2009-10-06, Ra?l S?nchez Siles rsanch...@infoglobal.es wrote: !!! And if anyone objects to GIT, please speak up ASAP !!! I think mercurial [0] could be a good option. It's a well known distributed VCS, maybe not as spread or known as git, but it's fulfilling most if not all general users

Re: [Openocd-development] Moving to git

2009-10-06 Thread Austin, Alex
-Original Message- From: openocd-development-boun...@lists.berlios.de [mailto:openocd- development-boun...@lists.berlios.de] On Behalf Of Grant Edwards Sent: Tuesday, October 06, 2009 12:52 PM To: openocd-development@lists.berlios.de Subject: Re: [Openocd-development] Moving to git

Re: [Openocd-development] Moving to git

2009-10-06 Thread Magnus Lundin
My impression, after using git just a little, is that it is a good tool, it takes some learning for effective use. For development work it seems that it gives me much better support for testing several different versions of experimental code than SVN so here it is a big step forward. I do not

Re: [Openocd-development] Moving to git

2009-10-05 Thread Øyvind Harboe
There was a suggestion for using Google groups to host the mailing list. I've had success with it in the past with projects like Symfony.  As long as the mailing list isn't hosted on Yahoo groups, I won't complain (LEON3 people do this and I don't like it). OK. Google groups is one

Re: [Openocd-development] Moving to git

2009-10-05 Thread David Brownell
On Monday 05 October 2009, Øyvind Harboe wrote: In short, the following will happen: 1. The source will be held in git. https://sourceforge.net/projects/openocd/ !!! And if anyone objects to GIT, please speak up ASAP !!! So far the only issue raised with $SUBJECT seems to be that we

Re: [Openocd-development] Moving to git

2009-10-05 Thread Øyvind Harboe
So the only thing we need to agree on *now* is to move git to sourceforge. No dissent heard so far on that one. I also believe there is a consensus that Berlios does not have the qualities we're looking for and that we need to either move away now or get a plan in place asap for migrating away.

Re: [Openocd-development] Moving to git

2009-10-05 Thread Austin, Alex
Since many people seem to not be fond of sourceforge, have you considered GitHub? Just put a README.markdown in the project and it will become a nice webpage front for the project. They already provide source browsing and snapshots available via HTTP, and make it trivially easy for anyone to (a)

Re: [Openocd-development] Moving to git

2009-10-05 Thread Michel Catudal
Le 05/10/2009 17:19, Øyvind Harboe a écrit : So the only thing we need to agree on *now* is to move git to sourceforge. I am supportive of the move to sourceforge. No dissent heard so far on that one. I also believe there is a consensus that Berlios does not have the qualities we're

Re: [Openocd-development] Moving to git

2009-10-05 Thread David Brownell
On Monday 05 October 2009, Austin, Alex wrote: Since many people seem to not be fond of sourceforge, AFAIK that's just the email. Which has issues like crappy archives, bad spam filtering, ads, and such. have you considered GitHub? In terms of GIT support is it significantly better than

Re: [Openocd-development] Moving to git

2009-10-05 Thread Xiaofan Chen
On Tue, Oct 6, 2009 at 2:36 AM, Dirk Behme dirk.be...@googlemail.com wrote: 3. the mailing list will be disabled and all openocd subscribers will receive an invitation to subscribe to the openocd mailing list at sourceforge. The sourceforge mailing list is the least sucky alternative for

Re: [Openocd-development] Moving to git

2009-10-05 Thread David Brownell
And in case anyone wants suggestions about how to start learning ... http://git-scm.com/course/svn.html That's addressed to folk more familiar with SVN than GIT. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] Moving to git

2009-10-05 Thread Xiaofan Chen
On Tue, Oct 6, 2009 at 7:37 AM, David Brownell davi...@pacbell.net wrote: On Monday 05 October 2009, Austin, Alex wrote: Since many people seem to not be fond of sourceforge, AFAIK that's just the email.  Which has issues like crappy archives, bad spam filtering, ads, and such. have you

Re: [Openocd-development] Moving to git

2009-10-05 Thread Austin, Alex
-Original Message- From: David Brownell [mailto:davi...@pacbell.net] Sent: Monday, October 05, 2009 6:37 PM To: openocd-development@lists.berlios.de Cc: Austin, Alex Subject: Re: [Openocd-development] Moving to git On Monday 05 October 2009, Austin, Alex wrote: Since many

Re: [Openocd-development] Moving to git

2009-10-05 Thread Øyvind Harboe
W.r.t. the choice of sourceforge for git: - we already have it running and tested there - there is no obviously superior alternative. If we switch every time we find something that is 10% better, we'll never get stability and a decision in place. Does anyone know a git hosting alternative that