From: Jimmy Guo <guo@cup.hp.com>
To: gdb@sourceware.cygnus.com
Subject: cvsup & sourceware repositories?
Date: Thu, 16 Mar 2000 16:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10003161728370.4096-100000@hpcll168.cup.hp.com> (raw)
<<sorry I sent the original question under a different subject line,
here it is again!>>
A general question about the repositories on sourceware:
Can we use cvsup client tool to maintain a local repository? Instead of
getting 'snapshots' via the CVS interfaces, I'd like to use the cvsup
tool to get updates to the repositories. It requires sourceware to run
a cvsupd daemon.
Otherwise, what is the easiest way to maintain local repository? I want
to create a local repository containing gdb, dejagnu, and binutils
products, and be able to automatically 'synchronize' with sourceware's
every night or on demand (turn-key solution here).
Thanks for any suggestion!
- Jimmy Guo, guo@cup.hp.com
WARNING: multiple messages have this Message-ID
From: Jimmy Guo <guo@cup.hp.com>
To: gdb@sourceware.cygnus.com
Subject: cvsup & sourceware repositories?
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10003161728370.4096-100000@hpcll168.cup.hp.com> (raw)
Message-ID: <20000401000000.8xilWZmF6QcZuNVMZuHq4FNVMOsOqD1Hgrs1mi1blio@z> (raw)
<<sorry I sent the original question under a different subject line,
here it is again!>>
A general question about the repositories on sourceware:
Can we use cvsup client tool to maintain a local repository? Instead of
getting 'snapshots' via the CVS interfaces, I'd like to use the cvsup
tool to get updates to the repositories. It requires sourceware to run
a cvsupd daemon.
Otherwise, what is the easiest way to maintain local repository? I want
to create a local repository containing gdb, dejagnu, and binutils
products, and be able to automatically 'synchronize' with sourceware's
every night or on demand (turn-key solution here).
Thanks for any suggestion!
- Jimmy Guo, guo@cup.hp.com
next reply other threads:[~2000-03-16 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 16:29 Jimmy Guo [this message]
2000-03-16 16:37 ` Jim Kingdon
2000-04-01 0:00 ` Russ Allbery
2000-04-01 0:00 ` Andrew Cagney
2000-04-01 0:00 ` Jimmy Guo
[not found] <Pine.LNX.4.10.10003161941510.6569-100000@hpcll168.cup.hp.com>
2000-03-16 19:03 ` Jimmy Guo
2000-03-16 22:45 Jimmy Guo
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=Pine.LNX.4.10.10003161728370.4096-100000@hpcll168.cup.hp.com \
--to=guo@cup.hp.com \
--cc=gdb@sourceware.cygnus.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