From: Miklos Vajna <vmiklos@frugalware.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Miklos Vajna <vmiklos@frugalware.org>
Subject: [PATCH] User Manual: document import-tars.perl
Date: Wed, 26 Sep 2007 00:37:04 +0200 [thread overview]
Message-ID: <1190759824-18896-1-git-send-email-vmiklos@frugalware.org> (raw)
In-Reply-To: <20070925201306.GW30845@fieldses.org>
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?
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
next prev parent reply other threads:[~2007-09-25 22:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:11 [PATCH] Remove 'submodules' from the TODO section of the User Manual Miklos Vajna
2007-09-25 19:23 ` J. Bruce Fields
2007-09-25 19:47 ` Miklos Vajna
2007-09-25 19:49 ` J. Bruce Fields
2007-09-25 19:57 ` Miklos Vajna
2007-09-25 20:02 ` J. Bruce Fields
2007-09-25 20:13 ` J. Bruce Fields
2007-09-25 20:16 ` J. Bruce Fields
2007-09-25 22:37 ` Miklos Vajna [this message]
2007-09-26 18:14 ` [PATCH] User Manual: document import-tars.perl J. Bruce Fields
2007-09-26 18:22 ` Miklos Vajna
2007-09-26 20:37 ` J. Bruce Fields
2007-09-26 19:58 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1190759824-18896-1-git-send-email-vmiklos@frugalware.org \
--to=vmiklos@frugalware.org \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).