infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <>
Subject [jira] [Commented] (INFRA-18499) Migrate primary VCS from SVN to Git for Apache JMeter
Date Mon, 17 Jun 2019 14:58:00 GMT


Daniel Gruno commented on INFRA-18499:

Vladimir, pardon me for jumping in on this matter, but you're going to have to explain why
you are in need of rewriting history. What is the problem you are trying to achieve, that
a new commit _after_ the existing ones will not solve?

> Migrate primary VCS from SVN to Git for Apache JMeter
> -----------------------------------------------------
>                 Key: INFRA-18499
>                 URL:
>             Project: Infrastructure
>          Issue Type: SVN->GIT Migration
>          Components: GitBox, Subversion
>            Reporter: Vladimir Sitnikov
>            Assignee: Chris Lambertus
>            Priority: Major
> There's an agreement to migrate from SVN to GitBox for Apache JMeter.
> Here's the vote thread:
> One of the ideas is to cleanup Git repository as a part of migration (e.g. remove accidentally
committed multi-megabyte jar files)
> Can you please clarify if that is a viable approach?
> My understanding is that it is valid to alter history (e.g. remove unrelated files) during
SVN->Git migration.
> Note: I do understand that "GitHub pull requests will need to be rebased", so the question
is more like "are there limitations on history edits during migration?"
> Current SVN:
> Desired Git:
> "git cleanup" is an automatic script:
> The result is as follows:
> As far as I understand, the process is as follows:
> * JMeter committers settle on a timeframe so they do not commit to SVN/Git repositories
> * Infra disables SVN->Git sync
> * Infra disables mail notifications for
> * Infra makes SVN repository a read-only one
> * Infra (or someone from JMeter comitters?) populates
> * Infra enables mail notifications for

This message was sent by Atlassian JIRA

View raw message