From: Hartmut Goebel <h.goebel@goebel-consult•de>
To: git@vger•kernel.org
Subject: migrating from svn: How to clean up history?
Date: Tue, 13 Dec 2011 15:53:09 +0100 [thread overview]
Message-ID: <4EE766D5.5040702@goebel-consult.de> (raw)
Hello,
I'm one of the developers of www.pyinstaller.org, a tool for
bundling/packagin Python scripts and al required modules into a single
executable for easy distribution. We are in the process of migrating
from Subversion to git.
Our SVN-Repo contains some stuff we do not want or do not need in the
git repo. How can we clean this up?
1) Useless commits e.g. tagging -> I want to remove these
2) copy or move mistakes -> I want to "correct" the copy
Example for 1): This occurs e.g. if this is done
svn cp trunk tags/v0.1 -m 'release v0.1' <<<--- this on in not needed
svn rm tags/v0.1 -m 'release v0.1'
svn cp trunk tags/v0.1 -m 'release v0.1'
In this case I want to completely eliminate the first commit.
Example for 2): This occurs e.g. if this is done
svn cp trunk tags/v0.1 -m 'release v0.1'
svn cp trunk tags/v0.1 -m 'release v0.1' <<-- actually copies to
tags/v0.1/trunk
In this case I want to change eliminate the first commit (this is he
same as case 1) and rewrite commit 2 to rewrite the path.
I already did some experiments with `git filter-branch` without success.
(I manage renaming the tags, though.)
Any hints how to to this clean-up?
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult ist Mitglied bei http://www.7-it.de
next reply other threads:[~2011-12-13 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 14:53 Hartmut Goebel [this message]
2011-12-13 15:12 ` migrating from svn: How to clean up history? Jakub Narebski
2011-12-16 23:11 ` Thomas Ferris Nicolaisen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE766D5.5040702@goebel-consult.de \
--to=h.goebel@goebel-consult$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox