Freddie Chopin wrote:
> As for the Debian "problem"... The maintainer of the package is -
> from what I remember - a member of this list and OpenOCD contributor.
I'm not primary maintainer, but well, I happen to do uploads from time
to time. I'm mostly speaking for myself here, but would like to
Freddie Chopin wrote:
> > rcs mean nothing.
>
> ... to you. The package with rc2 was downloaded from my website 100
> times in a week, while these -dev packages I post get downloaded at a
> much lower rate (package from 13 weeks ago was downloaded 700 times).
> But of course I'm Wrong and you a
W dniu 05.05.2013 21:34, Peter Stuge pisze:
> rcs mean nothing.
... to you. The package with rc2 was downloaded from my website 100
times in a week, while these -dev packages I post get downloaded at a
much lower rate (package from 13 weeks ago was downloaded 700 times).
But of course I'm Wrong
So it sounds like we have fixes pending that we can merge when they have
been tested.
I don't distinguish much between reverting broken commits and submitting
fixes as long as it's done right. Reverting and re-submitting a reworked
working commit is nicer from a timeliness and discipline point of
Freddie Chopin wrote:
> > Can we revert the changes that went into 0.7.0 and resubmit them to Gerrit?
>
> I'm confused... This discussion is about patches that are NOT in 0.7.0
> (fixes for building OpenOCD for ARM platform)
No Freddie, the discussion is about the brokenness in 0.7.0 which
those
I've uploaded Windows binaries to my website -
http://www.freddiechopin.info/ > Download > Software > OpenOCD
I've also added a post about the releaseon OpenOCD's website
http://openocd.sourceforge.net/2013/05/openocd-0-7-0-released/
Regards,
FCh
W dniu 05.05.2013 19:25, Øyvind Harboe pisze:
> Hi Peter,
>
> I've discovered that it takes a *LONG* time before teams learn that you
> *CAN* have the master branch be releasable at all times if you don't
> accept unfinished work or work that doesn't move the product forward.
>
> We *do* have the t
Hi Peter,
I've discovered that it takes a *LONG* time before teams learn that you
*CAN* have the master branch be releasable at all times if you don't accept
unfinished work or work that doesn't move the product forward.
We *do* have the tools and methods to keep track of unfinished work in
progr
Freddie Chopin wrote:
> > I could not disagree more with Freddie.
>
> How about you become a release manager for a bugfix release 0.7.1?
You already know that I favor keeping master releasable at all times,
and you also know that other contributors don't really agree with
that approach. Overall c
W dniu 2013-05-05 17:39, Peter Stuge pisze:
> I could not disagree more with Freddie.
How about you become a release manager for a bugfix release 0.7.1? I
know complaining is more fun, but...
4\/3!!
--
Get 100% visibili
Freddie Chopin wrote:
> > However, I would expect Debian (and other distro) people would be a
> > bit unhappy about FTBFS on some platforms (namely ARM), what is the
> > plan about it?
>
> The patches you posted were just a bit too late
I could not disagree more with Freddie. I think OpenOCD uses
On Sun, May 05, 2013 at 11:27:16AM +0200, Freddie Chopin wrote:
> W dniu 2013-05-05 11:20, Paul Fertser pisze:
>> However, I would expect Debian (and other distro) people would be a
>> bit unhappy about FTBFS on some platforms (namely ARM), what is the
>> plan about it?
>
> The patches you posted w
W dniu 2013-05-05 11:20, Paul Fertser pisze:
> However, I would expect Debian (and other distro) people would be a
> bit unhappy about FTBFS on some platforms (namely ARM), what is the
> plan about it?
The patches you posted were just a bit too late - I tried NOT to merge
any significant code cha
Hi,
On Sun, May 05, 2013 at 10:57:49AM +0200, Freddie Chopin wrote:
> OpenOCD-0.7.0 release is done! Files are available on sourceforge and
> relevant changes are in the repository.
Congratulations :)
However, I would expect Debian (and other distro) people would be a
bit unhappy about FTBFS on
14 matches
Mail list logo
