From: Kevin Geiss <kevin@desertsol.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-archimport
Date: Thu, 10 Nov 2005 14:49:59 -0700 [thread overview]
Message-ID: <20051110214959.GO9131@raven.localdomain> (raw)
In-Reply-To: <46a038f90511101332r3389734uc1aa1effd2898e15@mail.gmail.com>
ok. I tried this:
git-archimport kevin@desertsol.com--files/scripts--base kevin@desertsol.com--files/scripts--oco
and it always complains:
Cannot find patchset for 'kevin@desertsol.com--files/scripts--oco--0--patch-1' at /usr/bin/git-archimport line 784
I don't have any spaces or funny characters in filenames.
On Fri, Nov 11, 2005 at 10:32:12AM +1300, Martin Langhoff wrote:
> If the two branches are related, and you want the imported git
> branches to be related, do
>
> git-archimport arch-eduforge@catalyst.net.nz--2004/scripts
>
> that will bring all the stuff under scripts. If there are other
> branches or projects there that aren't related or you don't want to
> pull, do
>
> git-archimport arch-eduforge@catalyst.net.nz--2004/scripts--base \
> arch-eduforge@catalyst.net.nz--2004/scripts--oco
>
> In any case, you shoud never pass the last token (base-0). Also, if
> you have filenames with spaces or funny chars, you'll want a patch
> that I'm about to post.
>
> If you don't mind having this discussion on git@vger, could you
> forward it there?
>
> cheers,
>
>
> martin
>
> On 11/11/05, Kevin Geiss <kevin@desertsol.com> wrote:
> > hello, I was trying out the git-archimport script, I have a question.
> >
> > say I have two branches in tla (in the same archive):
> >
> > scripts--base--0
> > scripts--oco--0
> >
> > and scripts--oco--0--base-0 was tagged from scripts--base--0--patch-2.
> >
> > I first tried importing only the base branch, that worked fine. then
> > I started a new directory, and tried this:
> >
> > git arch-import -v archive/scripts--base--0 archive/scripts--oco--0
> >
> > and it keeps complaning about not being able to find scripts--oco--0--
> > patch-1. patch-1 is just a regular commit in the tla archive.
> > (patch-2 and patch-3 are merges from scripts--base)
> >
> > anyway, am I understanding the paradigm of the git-archimport script?
> > that I should expect it to be able to create a git repository for me
> > from these 2 branches?
> >
> > thanks for any info
> >
>
next parent reply other threads:[~2005-11-10 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D92ED0A1-B83A-43C3-B39C-AA8A21934D7F@desertsol.com>
[not found] ` <46a038f90511101332r3389734uc1aa1effd2898e15@mail.gmail.com>
2005-11-10 21:49 ` Kevin Geiss [this message]
2005-11-10 22:21 ` git-archimport Martin Langhoff
2005-11-11 5:19 ` git-archimport Kevin Geiss
2005-11-11 5:58 ` git-archimport Martin Langhoff
2005-11-11 23:24 ` git-archimport Kevin Geiss
2005-11-12 11:30 ` git-archimport Martin Langhoff
2010-02-18 18:13 RFD: git-bzr: anyone interested? Gabriel Filion
2010-02-18 18:37 ` Sverre Rabbelier
2010-02-19 7:05 ` Gabriel Filion
2010-02-19 13:55 ` Ilari Liusvaara
2010-02-22 4:42 ` Gabriel Filion
2010-02-22 10:51 ` Ilari Liusvaara
2010-02-23 3:20 ` Gabriel Filion
2010-02-23 12:45 ` Ilari Liusvaara
2010-04-26 21:41 ` Chris Packham
2010-08-06 7:19 ` Conrad Parker
2010-08-07 13:03 ` git-archimport (was: Re: RFD: git-bzr: anyone interested?) Jakub Narebski
2010-08-07 13:11 ` git-archimport Matthieu Moy
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=20051110214959.GO9131@raven.localdomain \
--to=kevin@desertsol.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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