[Openocd-development] 2nd Call For Papers, 18th Annual Tcl/Tk Conference 2011

2011-06-17 Thread Andreas Kupries
[[ Important Changes: The Conference Registration Page is live. Regarding special events we are looking into arranging a trip to the Air and Space Museum out near Dulles. This is currently a very tentative thing. If a local person would like to help with this please talk to "c...@c

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Jean-Christophe PLAGNIOL-VILLARD
On 12:32 Fri 17 Jun , Øyvind Harboe wrote: > > if possible a MAINTAINER file as done in the linux kernel > > Do you want to write up the definitions and procedures in a patch for > MAINTAINER file and then I can commit it to OpenOCD master branch > before we start this cycle? > > I think it w

[Openocd-development] [PATCH 2/2] build: do not included generated files in distribution

2011-06-17 Thread Spencer Oliver
From: Spencer Oliver We have to use this method as automake seems to ignore nodist_ on libs. Signed-off-by: Spencer Oliver --- src/Makefile.am |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/Makefile.am b/src/Makefile.am index 60d1189..e3adaad 100644 --- a/src/

[Openocd-development] [PATCH] more make dist tweaks

2011-06-17 Thread Spencer Oliver
Found some more missing files that should be included in the distribution. Cheers Spen [PATCH 1/2] build: add missing files to make dist [PATCH 2/2] build: do not included generated files in distribution This e-mail has bee

[Openocd-development] [PATCH 1/2] build: add missing files to make dist

2011-06-17 Thread Spencer Oliver
From: Spencer Oliver Signed-off-by: Spencer Oliver --- Makefile.am|9 +++-- doc/Makefile.am|3 ++- src/target/Makefile.am |1 - 3 files changed, 9 insertions(+), 4 deletions(-) diff --git a/Makefile.am b/Makefile.am index 2d07552..63ac5a1 100644 --- a/Makefi

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Øyvind Harboe
> if possible a MAINTAINER file as done in the linux kernel Do you want to write up the definitions and procedures in a patch for MAINTAINER file and then I can commit it to OpenOCD master branch before we start this cycle? I think it will be very good to have this written down as I'm sure all of

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Jean-Christophe PLAGNIOL-VILLARD
On 09:57 Fri 17 Jun , Øyvind Harboe wrote: > > so we do two tree the next tree (yours) and the release tree > > > > if multiple maintainer eed to merge code together they will send it the the > > RM > > in his next branch > > > > the description will be what must follow the release tree for th

[Openocd-development] [PATCH 2/2] build: pass correct flags to jimtcl during make distcheck

2011-06-17 Thread Spencer Oliver
From: Spencer Oliver This is only for the case of a make distcheck. During a normal release build these flags will be created by configure.gnu Signed-off-by: Spencer Oliver --- Makefile.am |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/Makefile.am b/Makefile.am inde

[Openocd-development] [PATCH 1/2] build: add missing files from dist release

2011-06-17 Thread Spencer Oliver
From: Spencer Oliver Signed-off-by: Spencer Oliver --- src/jtag/Makefile.am |3 ++- src/rtos/Makefile.am |3 +-- src/target/Makefile.am |7 ++- 3 files changed, 9 insertions(+), 4 deletions(-) diff --git a/src/jtag/Makefile.am b/src/jtag/Makefile.am index 2717dc5..d8a71e2 1

[Openocd-development] [PATCH] fix make distcheck

2011-06-17 Thread Spencer Oliver
I am going to commit the following two patches. This will also mean an upgrade of jimtcl when some other issues have been ironed out. They fix build issues when running make distcheck, still have a couple of remaining issues that i am working on. Cheers Spen [PATCH 1/2] build: add missing file

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Øyvind Harboe
> so we do two tree the next tree (yours) and the release tree > > if multiple maintainer eed to merge code together they will send it the the RM > in his next branch > > the description will be what must follow the release tree for the other tree > the maintainer manage his own way I am strugglin

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Jean-Christophe PLAGNIOL-VILLARD
On 08:39 Fri 17 Jun , Michael Schwingen wrote: > Am 06/17/2011 03:15 AM, schrieb Jean-Christophe PLAGNIOL-VILLARD: > > Hi all, > > > > I'd like to propose the following release cycle > > > > For the people familiar with Linux kernel its basically the same > > > > 2 development windo

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Jean-Christophe PLAGNIOL-VILLARD
On 09:03 Fri 17 Jun , Øyvind Harboe wrote: > On Fri, Jun 17, 2011 at 8:25 AM, Jean-Christophe PLAGNIOL-VILLARD > wrote: > > On 08:17 Fri 17 Jun     , Ųyvind Harboe wrote: > >> Some questions/comments: > >> > >> - if we look at the current way we work with OpenOCD, we just > >> commit stuff to

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Øyvind Harboe
On Fri, Jun 17, 2011 at 8:25 AM, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 08:17 Fri 17 Jun     , Ųyvind Harboe wrote: >> Some questions/comments: >> >> - if we look at the current way we work with OpenOCD, we just >> commit stuff to the master branch without regards to a release. >> I would li

Re: [Openocd-development] RFC Release Cycle

2011-06-17 Thread Michael Schwingen
Am 06/17/2011 03:15 AM, schrieb Jean-Christophe PLAGNIOL-VILLARD: > Hi all, > > I'd like to propose the following release cycle > > For the people familiar with Linux kernel its basically the same > > 2 development window: > merge window > fix window > > We will