Thank you Jakub! Forgot to look in the main git manpage, and that variable wasn't mentioned in the git-commit manpage or in any FAQ.. Now I have a more tricky question. The first part of my application history (the stone age) was maintained manually using tarballs, but the second part was maintained using CVS (the dark ages). I have successfully imported the CVS history using git-cvsimport, but now I want to add these older revisions that were made with tarballs to the same tree, before the CVS revisions. The last tarball and the first CVS revision have identical content, and I would like to somehow "glue" the histories together. Can this be done? Best regards, Magnus On Sun, 2008-08-31 at 04:12 -0700, Jakub Narebski wrote: > Magnus Hjorth <magnus.hjorth@xxxxxxx> writes: > > > Can someone tell me how to make a git commit with a date other than the > > current. I hope there is some easier way than changing the system > > clock.. :) > > See git(1), section "Environment Variables": > git Commits > GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, > GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, > EMAIL > see git-commit-tree(1) > > or you can use GIT_COMMITTER_IDENT, GIT_AUTHOR_IDENT. See output > of "git var -l" to get form of it. > > > I'm trying to port over old version history that I maintained manually > > (tarballs and changelogs) into a git repository. > > For that, I think it would be best to take a look at example > fast-import script: contrib/fast-import/import-tars.perl; > there is equivalent contrib/fast-import/import-zips.py if you > perfer either Pyhon over Perl, and/or zips over tarballs. > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
