From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Peter Karlsson <peter@softwolves.pp.se>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Importing non-version controlled bits and pieces to Git
Date: Fri, 20 Jun 2008 13:25:51 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806201323390.6439@racer> (raw)
In-Reply-To: <20080620115102.GW29404@genesis.frugalware.org>
Hi,
On Fri, 20 Jun 2008, Miklos Vajna wrote:
> On Fri, Jun 20, 2008 at 10:42:22AM +0100, Peter Karlsson <peter@softwolves.pp.se> wrote:
> > I am looking at moving a project that has not been version-controlled
> > in the regular sense into Git. I have found it to currently consist of
> > 40 directories with copies of the set of files in various shapes.
> >
> > I have reconstructed something that looks like a probable revision
> > tree for these 40 directories, and I want to put this into Git so that
> > I can examine what changes have been made where, and merge the various
> > versions back together so that there can be one version with all the
> > various fixes.
>
> Maybe contrib/fast-import/import-tars.perl?
BTW this is a relatively simple script showing how to import commits into
a Git repository using git-fast-import.
You should be able to use git-fast-import from a simple script yourself;
if you would like to see an example how to feed fast-import, just export a
few commits with "git fast-export HEAD~5..".
Hth,
Dscho
next prev parent reply other threads:[~2008-06-20 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 9:42 Importing non-version controlled bits and pieces to Git Peter Karlsson
2008-06-20 11:51 ` Miklos Vajna
2008-06-20 12:25 ` Johannes Schindelin [this message]
2008-06-20 12:42 ` Peter Karlsson
2008-06-20 12:57 ` Johannes Sixt
2008-06-20 13:00 ` Johannes Schindelin
2008-06-23 6:35 ` Peter Karlsson
2008-06-23 14:46 ` Peter Karlsson
2008-06-24 5:12 ` Karl Hasselström
2008-06-24 6:46 ` Peter Karlsson
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=alpine.DEB.1.00.0806201323390.6439@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
--cc=vmiklos@frugalware.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