| commit | 2594854b41c298ac89a1b9de34664db83b85ea7c | |
| author | mhagger <mhagger@be7e6eca-30d4-0310-a8e5-ac0d63af7087> | |
| Mon, 8 Mar 2010 15:41:04 +0000 (8 15:41 +0000) | ||
| committer | mhagger <mhagger@be7e6eca-30d4-0310-a8e5-ac0d63af7087> | |
| Mon, 8 Mar 2010 15:41:04 +0000 (8 15:41 +0000) | ||
| tree | 332bb333601c0054f7e449c694d9a94679e610ae | treesnapshot (tar.gz zip) |
| parent | e5a95bd0ffbeaa2ac432785d592e04afb4f22073 | commitdiff |
destroy_repository.py: Preserve empty/non-empty revisions.
Patch by: Jon Foster <jon.foster@cabot.co.uk>
With CVS, you can use "cvs commit -f" to commit a file that hasn't
actually changed. This generates a new revision in the repository,
with an empty diff. I'm working on a patch for cvs2svn to allow these
no-op CVS commits to be ignored.
I want to use contrib/destroy_repository.py to make test cases, but it
replaces every diff with an empty one. This means that every revision
(except adds and deletes) looks like a no-op CVS commit.
This change makes contrib/destroy_repository.py preserve the
empty/non-empty state, while still destroying the actual data.
git-svn-id: http://cvs2svn.tigris.org/svn/cvs2svn/trunk@5066 be7e6eca-30d4-0310-a8e5-ac0d63af7087
Patch by: Jon Foster <jon.foster@cabot.co.uk>
With CVS, you can use "cvs commit -f" to commit a file that hasn't
actually changed. This generates a new revision in the repository,
with an empty diff. I'm working on a patch for cvs2svn to allow these
no-op CVS commits to be ignored.
I want to use contrib/destroy_repository.py to make test cases, but it
replaces every diff with an empty one. This means that every revision
(except adds and deletes) looks like a no-op CVS commit.
This change makes contrib/destroy_repository.py preserve the
empty/non-empty state, while still destroying the actual data.
git-svn-id: http://cvs2svn.tigris.org/svn/cvs2svn/trunk@5066 be7e6eca-30d4-0310-a8e5-ac0d63af7087
| contrib/destroy_repository.py | diffblobblamehistory |