From: John Bent <johnbent@lanl.gov>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] git co old version
Date: Fri, 22 Apr 2011 14:03:20 -0600 [thread overview]
Message-ID: <1303502527-sup-8162@guava.lanl.gov> (raw)
In-Reply-To: <1303488368-sup-7145@tilus.net>
Excerpts from Tero Tilus's message of Fri Apr 22 10:14:09 -0600 2011:
> John Bent, 2011-04-22 17:29:
> > Can anyone supply the command-line magic to check out an old version
> > of sup from the git repository pls?
>
> To jump to specific tag (releases are tagged) you use `git checkout
> <tag>` and `git tag` to list tags.
>
Excellent. Thanks. Also, thanks to Mariano who replied separately with
the same solution. Also, thanks for tolerating what's clearly more
suited for a git message board!
But now a sup problem if you don't mind with sup-convert-ferret-index:
jvpn-132-106:~>sup-convert-ferret-index
/opt/local/lib/ruby1.9/gems/1.9.1/gems/sup-0.10.2/lib/sup/index.rb:229:in
`rescue in init': unknown index type "ferret": no such file to load --
ferret (RuntimeError)
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/sup-0.10.2/lib/sup/index.rb:224:in
`init'
from
/opt/local/lib/ruby1.9/gems/1.9.1/gems/sup-0.10.2/bin/sup-convert-ferret-index:53:in
`<top (required)>'
from /opt/local/bin/sup-convert-ferret-index:19:in `load'
from /opt/local/bin/sup-convert-ferret-index:19:in `<main>'
Anyone see this before? I'm doing something silly probably.
--
Thanks,
John
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-04-22 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 14:29 John Bent
2011-04-22 16:14 ` Tero Tilus
2011-04-22 20:03 ` John Bent [this message]
2011-04-23 9:25 ` Tero Tilus
2011-04-26 16:30 ` John Bent
2011-04-26 18:33 ` Tero Tilus
2011-05-12 3:28 ` John Bent
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=1303502527-sup-8162@guava.lanl.gov \
--to=johnbent@lanl.gov \
--cc=sup-talk@rubyforge.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