Signed-off-by: Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> --- On Tue, Sep 25, 2007 at 04:13:06PM -0400, "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > One exception--the "series of tarballs" thing--I think it's cool that > you can just unpack a bunch of tarballs and string them together into a > git history. It gives a good sense of how git works, and I don't think > it's documented explicitly anywhere. I think that might be kinda fun to > write up. But I haven't tried. something like this? VMiklos Documentation/user-manual.txt | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index a085ca1..f722932 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -978,6 +978,19 @@ $ git add . # include everything below ./ in the first commit: $ git commit ------------------------------------------------- +If you already have a series of tarballs (typically previous releases without +using a version control system): + +------------------------------------------------- +$ mkdir project +$ cd project +$ git init +$ perl import-tars.perl /path/to/tarballs/*.tar.bz2 +$ git checkout import-tars +------------------------------------------------- + +You can find `import-tars.perl` in the `contrib/fast-import/` directory. + [[how-to-make-a-commit]] How to make a commit -------------------- -- 1.5.3.2.80.g077d6f-dirty - 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
