Re: [Valgrind-users] Migrating Valgrind sources from SVN to GIT

2017-08-04 Thread Mark Wielaard 
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 available for
> you to test.

I might have made a mistake by trying to compress the new git
repository on the server with git gc --aggressive. I probably should
have used git repack instead. It looks like the git gc pruned some
VEX branches. I thought I was working on a copy, but I had copied
a symlink to the bare git repository, not the directory itself...

(It did seem to compress from 750MB down to 40MB, but if that means
some branches were deleted that is not good of course...)

> How the test migration was performed:
> ~~
> See recipes at https://github.com/ivosh/valgrind-git-migration

I'll follow that to recreate the git repository with all branches
and put it back on sourceware.

Apologies,

Mark

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Re: [Valgrind-users] Migrating Valgrind sources from SVN to GIT

2017-03-04 Thread Ivo Raisr 
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 comments have been received.
Necessary infrastructure changes in Valgrind code repo and Valgrind
www repo were prepared,
together with the migration recipe.

Please review them all here: https://github.com/ivosh/valgrind-git-migration

1. Migration recipe itself:
https://github.com/ivosh/valgrind-git-migration/blob/master/migration-recipe.txt

2. Necessary Valgrind code repo changes:
https://github.com/ivosh/valgrind-git-migration/blob/master/001-Change-SVN-to-GIT-in-various-places.patch
https://github.com/ivosh/valgrind-git-migration/blob/master/002-Update-auxprogs-update-demangler-for-Valgrind-in-GIT.patch
https://github.com/ivosh/valgrind-git-migration/blob/master/003-Fix-nightly-build-script-to-work-with-git.patch
https://github.com/ivosh/valgrind-git-migration/blob/master/004-fix-verbose-version-reporting-for-git.patch
https://github.com/ivosh/valgrind-git-migration/blob/master/005-Change-Subversion-to-GIT-in-various-places.patch
https://github.com/ivosh/valgrind-git-migration/blob/master/006-Convert-release-HOWTO.txt-from-SVN-to-GIT.patch

3. Website changes (residing in valgrind-www SVN repository):
https://github.com/ivosh/valgrind-git-migration/blob/master/valgrind-www-changes.patch

Please provide your comments and suggestions.
We are very close to the final migration!

I.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Re: [Valgrind-users] Migrating Valgrind sources from SVN to GIT

2017-02-28 Thread Ivo Raisr 
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):
>>
>> [receive]
>> denyNonFastforwards = true
>
>
> That doesn't actually prevent people pushing merges though, it just stops
> history being rewritten - the push to the remote can only move the remote
> forward but the pushed commits can include merges.

Good point.
So I think it's the time to start gathering config for AdaCore git hooks [1] [2]
which is used at sourceware.org.

--
[hooks]
from-domain = sourceware.org
mailinglist = valgrind-develop...@lists.sourceforge.net

# Allow to include debugging output in commit messages.
max-rh-line-length = 0

# Forces to rebase changes before pushing to master and release branches.
reject-merge-commits = refs/heads/master, refs/heads/VALGRIND_.*

commit-url = "https://sourceware.org/git/?p=valgrind.git;h=%(rev)s"

# No emails from private user branches.
no-emails = /refs/heads/user/.*
--

Your thoughts?
I.


[1] https://github.com/adacore/git-hooks
[2] https://sourceware.org/gdb/wiki/GitHooksUsersGuide

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Re: [Valgrind-users] Migrating Valgrind sources from SVN to GIT

2017-02-28 Thread 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):
>
> [receive]
> denyNonFastforwards = true

That doesn't actually prevent people pushing merges though, it just 
stops history being rewritten - the push to the remote can only move the 
remote forward but the pushed commits can include merges.

Tom

-- 
Tom Hughes (t...@compton.nu)
http://compton.nu/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users