# [PATCH] import-tars: separate author from committer 2 messages from 2009-03-20 to 2009-03-20. Participants: Giuseppe Bilotta, Shawn O. Pearce. Thread: https://gitlist.dev/t/18432 ## Giuseppe Bilotta, 2009-03-20 09:57 Subject: [PATCH] import-tars: separate author from committer Message-ID: <1237543070-4909-1-git-send-email-giuseppe.bilotta@gmail.com> URL: https://gitlist.dev/e/1237543070-4909-1-git-send-email-giuseppe.bilotta%40gmail.com ``` The import-tars script is typically employed to (re)create the past history of a project from stored tars. Although assigning authorship in these cases can be a somewhat arbitrary process, it makes sense to set the author to whoever created the tars in the first place (if it's known), and (s)he can in general be different from the committer (whoever is running the script). Implement this by having separate author and committer data, making them settable from the usual GIT_* environment variables. --- Or should I have made the ENV access a separate patch? contrib/fast-import/import-tars.perl | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git a/contrib/fast-import/import-tars.perl b/contrib/fast-import/import-tars.perl index 23aeb25..6309d14 100755 --- a/contrib/fast-import/import-tars.perl +++ b/contrib/fast-import/import-tars.perl @@ -14,13 +14,18 @@ die "usage: import-tars *.tar.{gz,bz2,Z}\n" unless @ARGV; my $branch_name = 'import-tars'; my $branch_ref = "refs/heads/$branch_name"; -my $committer_name = 'T Ar Creator'; -my $committer_email = 'tar@example.com'; +my $author_name = $ENV{'GIT_AUTHOR_NAME'} || 'T Ar Creator'; +my $author_email = $ENV{'GIT_AUTHOR_EMAIL'} || 'tar@example.com'; +my $committer_name = $ENV{'GIT_COMMITTER_NAME'} || `git config --get user.name`; +my $committer_email = $ENV{'GIT_COMMITTER_EMAIL'} || `git config --get user.email`; + +chomp($committer_name, $committer_email); open(FI, '|-', 'git', 'fast-import', '--quiet') or die "Unable to start git fast-import: $!\n"; foreach my $tar_file (@ARGV) { + my $commit_time = time; $tar_file =~ m,([^/]+)$,; my $tar_name = $1; @@ -39,7 +44,7 @@ foreach my $tar_file (@ARGV) die "Unrecognized compression format: $tar_file\n"; } - my $commit_time = 0; + my $author_time = 0; my $next_mark = 1; my $have_top_dir = 1; my ($top_dir, %files); @@ -92,7 +97,7 @@ foreach my $tar_file (@ARGV) } $files{$path} = [$next_mark++, $mode]; - $commit_time = $mtime if $mtime > $commit_time; + $author_time = $mtime if $mtime > $author_time; $path =~ m,^([^/]+)/,; $top_dir = $1 unless $top_dir; $have_top_dir = 0 if $top_dir ne $1; @@ -100,6 +105,7 @@ foreach my $tar_file (@ARGV) print FI < $author_time +0000 committer $committer_name <$committer_email> $commit_time +0000 data < $commit_time +0000 +tagger $author_name <$author_email> $author_time +0000 data < URL: https://gitlist.dev/e/20090320144352.GZ23521%40spearce.org In-Reply-To: <1237543070-4909-1-git-send-email-giuseppe.bilotta@gmail.com> ``` Giuseppe Bilotta wrote: > The import-tars script is typically employed to (re)create the past > history of a project from stored tars. Although assigning authorship in > these cases can be a somewhat arbitrary process, it makes sense to set > the author to whoever created the tars in the first place (if it's > known), and (s)he can in general be different from the committer > (whoever is running the script). > > Implement this by having separate author and committer data, making them > settable from the usual GIT_* environment variables. > --- > > Or should I have made the ENV access a separate patch? Looks fine to me. Acked-by: Shawn O. Pearce -- Shawn. ```