From: Johannes Gilger <heipei@hackvalue.de>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-import.sh using git-fast-import
Date: Mon, 27 Aug 2007 19:44:44 +0200 [thread overview]
Message-ID: <46D30D8C.204@hackvalue.de> (raw)
In-Reply-To: <fcaeb9bf0708270913o37b2dbdfw2f5f7d89d9ab1d21@mail.gmail.com>
Hi,
nice of you to share, but i think the policy on this mailing list is to
include patches (and probably shellscripts like your's) in the message
itself rather than create a file attachment. I for one find it much more
convenient.
regards, jojo
Nguyen Thai Ngoc Duy wrote:
> It is not really good. It does not run as fast as git-add &&
> git-commit. But it can swallow big directories that git-add &&
> git-commit can't. So I think I would share. It's also simpler than
> those in contrib/fast-import, making it a good start for
> git-fast-import's new users.
>
> To run it, move inside the directory you want to import then type
> ./git-import.sh master 'your import message'
next prev parent reply other threads:[~2007-08-27 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 16:13 git-import.sh using git-fast-import Nguyen Thai Ngoc Duy
2007-08-27 17:44 ` Johannes Gilger [this message]
[not found] ` <20070828035430.GJ18160@spearce.org>
[not found] ` <20070828055431.GA28311@coredump.intra.peff.net>
[not found] ` <20070828061118.GO18160@spearce.org>
[not found] ` <20070828063316.GB5444@coredump.intra.peff.net>
[not found] ` <20070829034725.GR18160@spearce.org>
[not found] ` <20070829041120.GA25779@coredump.intra.peff.net>
2007-08-29 15:20 ` Nicolas Pitre
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=46D30D8C.204@hackvalue.de \
--to=heipei@hackvalue.de \
--cc=git@vger.kernel.org \
/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).