I would really, really, really, like to get some testing feedback
from anybody so the entire release is not based on my own efforts,
which might miss something.
- rob -
Has anybody offered to test yet?
I am a really amateur user with an AMD64 and use mostly FreeBSD. I
On 08/24/10 20:15, Nathan Peet Maier wrote:
Has anybody offered to test yet?
The release went out a few days ago, but thanks for offering. :-)
I am a really amateur user with an AMD64 and use mostly FreeBSD. I
haven't picked too much up on what testing is all about. Do you use
bug
On 08/13/10 10:21, strk wrote:
On Fri, Aug 13, 2010 at 08:40:44AM -0600, Rob Savoye wrote:
I did minimal BSD testing, and fixed a few minor problems with missing
include files. FreeBSD and NetBSD are fine, OpenBSD I give up on till
they fix the version of Boost and GCC to something that
On Thu, Aug 12, 2010 at 09:55:25PM -0600, Rob Savoye wrote:
If any BSD users out there can test the release branch, I'd appreciate
it. I'll get around to it next week now that the release branch is
mostly stabilized, but I'd need to upgrade my builds slaves to the most
recent versions, which
On Fri, Aug 13, 2010 at 6:50 AM, strk s...@keybit.net wrote:
At least with git version 1.6.0.2 I belive the branch command
should also specify which remote branch to track, or will be
a private branch with that name, so I had to do this:
$ git clone git://git.sv.gnu.org/gnash.git
$ git
On 08/13/10 04:50, strk wrote:
On Thu, Aug 12, 2010 at 09:55:25PM -0600, Rob Savoye wrote:
At least with git version 1.6.0.2 I belive the branch command
should also specify which remote branch to track, or will be
a private branch with that name, so I had to do this:
$ git clone
On Fri, Aug 13, 2010 at 08:40:44AM -0600, Rob Savoye wrote:
And I think this helps merging: (still learning git)
[branch release_0_8_8]
remote = origin
merge = refs/heads/release_0_8_8
I belive the above lines are what you get by adding
the second argument to checkout or branch
7 matches
Mail list logo
