On Fri, Aug 04, 2017 at 08:14:19PM +0200, Ivo Raisr wrote:
> Where I will find the new repo:
> ~~~
> At sourceware.org. Precisely at:
> git://sourceware.org/git/valgrind.git/
> http://sourceware.org/git/valgrind.git/
> Right now a snapshot of SVN sources as of 2017-06-26 is
Dear Valgrind community,
I am happy to announce that migration of Valgrind sources from
existing Subversion SCM to modern git SCM will happen 14th August
2017.
What is going on now?
~
The migration has been tested and all infrastructure is in place now.
We still use the official
Dear Valgrind community,
Now that Valgrind release 3.13.0 is out, we are pleased to announce
an imminent migration of Valgrind sources from existing Subversion SCM
to modern git SCM, as discussed during our FOSDEM 2017 Valgrind devroom
and announced publicly back at the end of February 2017.
2017-02-24 20:21 GMT+01:00 Ivo Raisr :
> Dear Valgrind community,
>
> We are pleased to announce an imminent migration of Valgrind sources
> from existing Subversion SCM to modern git SCM, as discussed during
> our FOSDEM 2017 Valgrind devroom.
So far a number of very useful
2017-02-28 23:13 GMT+01:00 Tom Hughes :
> On 28/02/17 20:56, Ivo Raisr wrote:
>
>> So we decided to stick with existing (SVN) workflow which translates to
>> "rebased branches at the top of the tree".
>> Our valgrind.git config will have (after the final migration happens):
>>
>>
On 28/02/17 20:56, Ivo Raisr wrote:
> So we decided to stick with existing (SVN) workflow which translates to
> "rebased branches at the top of the tree".
> Our valgrind.git config will have (after the final migration happens):
>
> [receive]
> denyNonFastforwards = true
That doesn't
Dear Valgrind community,
We are pleased to announce an imminent migration of Valgrind sources
from existing Subversion SCM to modern git SCM, as discussed during
our FOSDEM 2017 Valgrind devroom.
What is going on now?
~
The migration has just started. We are now in beta testing