git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kevin Geiss <kevin@desertsol.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Kevin Geiss <kevin@desertsol.com>, git@vger.kernel.org
Subject: Re: git-archimport
Date: Thu, 10 Nov 2005 22:19:10 -0700	[thread overview]
Message-ID: <20051111051910.GP9131@raven.localdomain> (raw)
In-Reply-To: <46a038f90511101421o7988a1bfi89eb0e33bd34e4bb@mail.gmail.com>

On Fri, Nov 11, 2005 at 11:21:12AM +1300, Martin Langhoff wrote:
> On 11/11/05, Kevin Geiss <kevin@desertsol.com> wrote:
> > Cannot find patchset for 'kevin@desertsol.com--files/scripts--oco--0--patch-1' at /usr/bin/git-archimport line 784
> 
> Hmmm. The script uses tla itself to get the patch. What happens if you do
> 
>   tla get-changeset -A kevin@desertsol.com--files/scripts--oco--0--patch-1
> 
> In short, you must have a recent tla configured and with the archive
> registered.
> 
> cheers,
> 
> 
> 
> martin

I've got tla 1.3, and the changeset seems to be there:

10:15pm0raven>tla get-changeset -A kevin@desertsol.com--files/scripts--oco--0--patch-1                                         /tmp
usage: tla get-changeset [options] revision [dir]
try get-changeset --help
10:15pm1raven>tla get-changeset  kevin@desertsol.com--files/scripts--oco--0--patch-1                                           /tmp
gpg: Signature made Mon Feb 14 12:28:10 2005 MST using DSA key ID E1E6A3B1
gpg: Good signature from "Kevin Geiss <kevin@desertsol.com>"
10:15pm0raven>tla get-changeset --help                                                                                         /tmp
retrieve a changeset from an archive
usage: tla get-changeset [options] revision [dir]

  -h, --help     Display a help message and exit.
  -H             Display a verbose help message and exit.
  -V, --version  Display a release identifier string
                 and exit.
  -A, --archive  Override `my-default-archive'

10:16pm0raven>tla --version                                                                                                    /tmp
tla lord@emf.net--gnu-arch-2004/dists--tla--1.3--version-0(configs/gnu/This-release) from regexps.com

  reply	other threads:[~2005-11-11  5:19 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   ` git-archimport Kevin Geiss
2005-11-10 22:21     ` git-archimport Martin Langhoff
2005-11-11  5:19       ` Kevin Geiss [this message]
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

  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=20051111051910.GP9131@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.
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).