Re: [PATCH] User Manual: document import-tars.perl
On Wed, Sep 26, 2007 at 12:37:04AM +0200, Miklos Vajna wrote:
Show 11 quoted lines
> Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
> ---
>
> On Tue, Sep 25, 2007 at 04:13:06PM -0400, "J. Bruce Fields" <bfields@fieldses.org> 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?
Neat-o, I'd missed (or forgotten about) import-tars.perl.
But I'd prefer to keep this first explanation of how to initialize and commit to a new project pretty streamlined, and I don't think this is really necessary here. So let's save this up until we have enough material for a separate chapter or section on interacting with other scm's.
--b.
Show 33 quoted lines
>
> 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
>
Miklos Vajna