diff options
author | Martin Langhoff <martin@catalyst.net.nz> | 2005-09-04 22:55:29 +1200 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2005-09-04 10:28:43 -0700 |
commit | 52586ecb16f2158de29daabb0ed72b094ca8d5cc (patch) | |
tree | 2fbf032d246a8f6ae02a674efd8f78e108ac2f30 | |
parent | 3292ae4794012994560816e6111d27c809f5e86a (diff) | |
download | git-52586ecb16f2158de29daabb0ed72b094ca8d5cc.tar.gz git-52586ecb16f2158de29daabb0ed72b094ca8d5cc.tar.xz |
[PATCH] archimport: avoid committing on an Arch tag
Arch tags are full commits (without any changed files) as well. Trust Arch
to have put an unchanged tree in place (which seems to do reliably), and
just add a tag & new branch. Speeds up Arch imports significantly, and leaves
history in a much saner state.
Signed-off-by: Martin Langhoff <martin@catalyst.net.nz>
Signed-off-by: Junio C Hamano <junkio@cox.net>
-rwxr-xr-x | git-archimport-script | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/git-archimport-script b/git-archimport-script index 3c8aab74b..8f475fd66 100755 --- a/git-archimport-script +++ b/git-archimport-script @@ -227,6 +227,14 @@ foreach my $ps (@psets) { # find where we are supposed to branch from `git checkout -b $ps->{branch} $branchpoint`; + + # If we trust Arch with the fact that this is just + # a tag, and it does not affect the state of the tree + # then we just tag and move on + tag($ps->{id}, $branchpoint); + ptag($ps->{id}, $branchpoint); + print " * Tagged $ps->{id} at $branchpoint\n"; + next; } die $! if $?; } |