From: "Philip Oakley" <philipoakley@iee.org>
To: "Philip Oakley" <philipoakley@iee.org>,
"Tomas Carnecky" <tom@dbservice.com>,
"nn6eumtr" <nn6eumtr@gmail.com>
Cc: "Git List" <git@vger.kernel.org>
Subject: Re: How to deal with historic tar-balls
Date: Mon, 2 Jan 2012 10:07:47 -0000 [thread overview]
Message-ID: <4C50794C7EED42A0B1A25ABD77CE7DB0@PhilipOakley> (raw)
In-Reply-To: B375E525C4704EA8807B5A59257B690B@PhilipOakley
From: "Philip Oakley" <philipoakley@iee.org>: Sunday, January 01, 2012 6:30
PM
> From: "Tomas Carnecky" <tom@dbservice.com> : Sunday, January 01, 2012
> 12:27 AM
>>On 12/31/11 8:04 PM, nn6eumtr wrote:
>>> I have a number of older projects that I want to bring into a git
>>> repository. They predate a lot of the popular scm systems, so they are
>>> primarily a collection of tarballs today.
>> There is a script which will import sources from multiple tarballs,
>> creating a commit with the contents of each tarball. It's in the git
>> repository under contrib/fast-import/import-tars.perl.
> I wasn't aware of those scripts. I'll be having a look at the zip import
> script for my needs.
>
>> tom
> Philip
>
I had a look at the script but Python isn't part of the Msysgit install, so
the example wouldn't run.
Also I couldn't see how the "fast_import.write(" method was being created -
my ignorance of Python? Otherwise I could look at scripting it.
Philip
next prev parent reply other threads:[~2012-01-02 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 19:04 How to deal with historic tar-balls nn6eumtr
2012-01-01 0:27 ` Tomas Carnecky
2012-01-01 18:30 ` Philip Oakley
2012-01-01 20:54 ` Philip Oakley
2012-01-02 10:07 ` Philip Oakley [this message]
2012-01-02 18:26 ` Dirk Süsserott
2012-01-04 20:04 ` Philip Oakley
2012-01-01 19:04 ` Dirk Süsserott
2012-01-05 15:25 ` Neal Kreitzinger
2012-01-07 1:10 ` nn6eumtr
2012-01-07 1:50 ` Thomas Rast
2012-01-07 19:18 ` Neal Kreitzinger
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=4C50794C7EED42A0B1A25ABD77CE7DB0@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=nn6eumtr@gmail.com \
--cc=tom@dbservice.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).