From: "Eric S. Raymond" <esr@thyrsus.com>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: git@vger.kernel.org
Subject: Re: Requirements for integrating a new git subcommand
Date: Fri, 23 Nov 2012 10:35:41 -0500 [thread overview]
Message-ID: <20121123153541.GA20097@thyrsus.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211231022440.1431@ds9.cixit.se>
Peter Krefting <peter@softwolves.pp.se>:
> I was just about to say that the import direction of this seems to
> fill the same need as contrib/fast-import/import-directories.perl
> that I submitted a few years back.
Yours was the closest in functionality, yes.
> Your version seems only to be able to import a linear history,
> however, my tool does support creating merge commits (basically, the
> history I had to import was very messy and contained a lot of
> snapshot directories having been worked on in parallel).
git-weave can *weave* (import) a sequence with merge commits, as your
tool can. What it can't do is unravel a nonlinear repo into a tree
sequence that will round-trip through the weave operation. (Though I
thought of a way I might be able to fix that last night.)
> Anyway, my sentiment is that if you can add support for merges in
> you weave tool, then I am very much for removing my old script from
> the repository.
The support is there. I will take this as direction to (a) add a
test load demonstrating this, and (b) include the removal of
import-directories.perl in my integration patch.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-11-23 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 5:30 Requirements for integrating a new git subcommand Eric S. Raymond
2012-11-22 19:17 ` Shawn Pearce
2012-11-22 22:11 ` Eric S. Raymond
2012-11-23 9:13 ` Michael J Gruber
2012-11-23 15:53 ` Eric S. Raymond
2012-11-23 20:21 ` Christian Couder
2012-11-23 16:29 ` Eric S. Raymond
2012-11-23 9:27 ` Peter Krefting
2012-11-23 15:35 ` Eric S. Raymond [this message]
2012-11-26 11:01 ` Peter Krefting
2012-11-26 2:57 ` Junio C Hamano
2012-11-26 4:49 ` Eric S. Raymond
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121123153541.GA20097@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).