git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Karlsson <peter@softwolves.pp.se>
To: git@vger.kernel.org
Subject: Hand-rolling migration to Git
Date: Tue, 25 Mar 2008 11:03:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803251056570.8472@ds9.cixit.se> (raw)

Hi!

I am looking for documentation on how to hand-roll a conversion to Git,
but I keep getting lost in the maze of similar-looking man pages. Is
there a tutorial, howto, or perhaps even just a list of recommended man
pages to read on importing project changes to Git?

I have projects of two different kinds that I need to import:

1. The "make a copy of the source code directory and edit the new copy"
source management system. I need to be able to import one directory at
a time, each describing a version controlled state. The date stamp on
the commits should probably be the most recent file in each directory.

2. A piece of software using PVCS (a RCS-like version control system
with added support for parallel development (using a locking model)). I
have a complete "trail file" which lists all commits done to the
repository in chronological order since the repository was created, and
can use that as a base. Since it has no concept of an atomic commit, I
need to semi-manually join commits by walking the trail file and
comparing lock sets, time stamps, commit messages and authors.

I can probably make the output from (2) look like from (1), so I
basically just need to find a pointer to information on how to
(re-)create the history with Git.

-- 
\\// Peter - http://www.softwolves.pp.se/

             reply	other threads:[~2008-03-25 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 10:03 Peter Karlsson [this message]
2008-03-25 10:14 ` Hand-rolling migration to Git Johan Herland
2008-03-25 10:39   ` Johannes Schindelin
2008-03-31  6:23     ` 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=Pine.LNX.4.64.0803251056570.8472@ds9.cixit.se \
    --to=peter@softwolves.pp.se \
    --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).