git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: GIT <git@vger.kernel.org>, Catalin Marinas <catalin.marinas@gmail.com>
Subject: arch2git import script
Date: Wed, 24 Aug 2005 01:11:57 +1200	[thread overview]
Message-ID: <46a038f90508230611337c695e@mail.gmail.com> (raw)

First draft of an Arch import. Very limited but will import one
"branch" into one head. The basics are for it to follow branches, and
some support for marking merges (or at least what git would consider
merges.

TODO:
- proper branch switching
- binary file handling
- get the date format right!
- parse the output of cat-archive-log to know what files to add/delete
and cleanup the logmsg
- ensure all shell invocations have error handling
- allow multiple "Archives"
- learn to run repeatedly over the same git repo, importing only new commits
- track cherrypicking to identify how far branches are merged (in the
git sense)
- a few options as to how to follow (or not) the history
  - follow a full branch starting from a full import "down" with
branches opening from it.
  - follow a branch history "up"

An example invocation to import the sears-ldap-dev branch is:

  mkdir sample-import
  cd sample-import;
  git-archimport-script -t /tmp/some/dir -i \
      -A arch-eduforge@catalyst.net.nz--2004 sears-ldap--dev

the commit message needs cleanup, the dates are bogus, and we aren't
marking deletes... but it otherwise works great! ;)

cheers,


martin

             reply	other threads:[~2005-08-23 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 13:11 Martin Langhoff [this message]
2005-08-23 13:13 ` arch2git import script Martin Langhoff

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=46a038f90508230611337c695e@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --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).