From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-user@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: JIT compiler
Date: Mon, 09 Jan 2006 13:47:20 +0100 [thread overview]
Message-ID: <87irst8t5z.fsf@laas.fr> (raw)
In-Reply-To: <20060109122542.4dbc58d4@faust> (David Pirotte's message of "Mon, 9 Jan 2006 12:25:42 +0100")
David Pirotte <david@altosw.be> writes:
>> $ tla get lcourtes@laas.fr--2004-libre/guile-vm--revival--0.6 guile-vm
>>
>> ^ ^ ^
>> | | |
>> name of the archive name of the branch directory
>> you just registered you wanna get
>
> is there a similar command to (once you registered) get the latest...:
>
> cd <cvs checkout location>
> cvs update -d
>
> that I could understand and use :-) [and remember :-)]
Sure, and it's called `update'. :-) To summarize:
# Teach tla that some archive (or ``repository'') is available at URI.
$ tla register-archive URI
# At this point, it knows that an archive named
# `blah@blah.org--SOME-ARCHIVE' is available at URI.
# From now on, you will always use this name and not the URI.
# You can now get files from that archive.
$ tla get blah@blah.org--SOME-ARCHIVE/C--B--V DIR
# This retrieves the latest version of the branch C--B--V into
# directory DIR.
$ cd DIR
# Updating the local copy, as with `cvs update':
$ tla update
It's not all that complicated. All you need is to be aware of certain
conventions, some of which are, well, quite unusual (some might say
``weird''). ;-) Most importantly, you need to know that
``repositories'' are usually called ``archives'', and that a particular
naming scheme is enforced for branch names, namely
CATEGORY--BRANCH--VERSION. And yes, conventions in GNU Arch are a
controversial topic.
More information is available in the (slightly outdated) tutorial:
http://www.gnu.org/software/gnu-arch/tutorial/arch.html .
Thanks,
Ludovic.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-01-09 12:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 0:37 JIT compiler Leonardo Lopes Pereira
2005-12-30 13:14 ` Neil Jerram
2006-01-03 10:30 ` Ludovic Courtès
2006-01-07 22:31 ` Neil Jerram
2006-01-08 15:43 ` Han-Wen Nienhuys
2006-01-09 9:13 ` Ludovic Courtès
2006-01-09 10:54 ` Neil Jerram
2006-01-09 11:25 ` David Pirotte
2006-01-09 12:47 ` Ludovic Courtès [this message]
2006-01-09 22:52 ` Neil Jerram
2006-01-10 8:38 ` Ludovic Courtès
2006-01-10 9:20 ` Neil Jerram
2006-01-10 17:35 ` Aaron VanDevender
2006-01-10 21:47 ` Marius Vollmer
2006-01-11 8:32 ` Ludovic Courtès
[not found] <E1EsL1F-0006hc-Lg@pat.uio.no>
2006-01-04 21:14 ` Kjetil S. Matheussen
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: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87irst8t5z.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).