Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: using rsync to create local repository
Date: Wed, 01 Feb 2006 23:43:00 -0000	[thread overview]
Message-ID: <20060201234306.GD14187@nevyn.them.org> (raw)
In-Reply-To: <1138318142.1423.70.camel@dufur.beaverton.ibm.com>

On Thu, Jan 26, 2006 at 03:29:02PM -0800, PAUL GILLIAM wrote:
> +Under rare circumstances, it is desirable to maintain a local copy of
> +the complete CVS repository.  Anonymous <code>rsync</code> access has
> +been is available for that purpose.  Here is how to get a copy of the
> +repository, or to synchronize an existing one:

"has been is"; probably just want "is".

> +
> +<pre>
> +rsync --archive --delete --compress rsync://sources.redhat.com/src-cvs src-cvs </pre> 

That's not the command you were using, is it?  There were some
--exclude options; without them you can't check out of the resulting
tree and you waste a lot of bandwidth.

> +
> +You can get <code>rsync</code> or learn more about it from its home page:
> +<a href:"http://rsync.samba.org"> rsync.samba.org</a>

Extra space before rsync.samba.org.  There's supposed to be an = after
href.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-02-01 23:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1138301788.1423.54.camel@dufur.beaverton.ibm.com>
     [not found] ` <20060126190733.GA13020@nevyn.them.org>
     [not found]   ` <1138308820.1423.59.camel@dufur.beaverton.ibm.com>
     [not found]     ` <20060126205524.GA17357@nevyn.them.org>
2006-01-26 23:28       ` PAUL GILLIAM
2006-02-01 23:43         ` Daniel Jacobowitz [this message]
2006-02-03 22:58           ` PAUL GILLIAM
2006-02-06 21:20             ` Daniel Jacobowitz

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=20060201234306.GD14187@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pgilliam@us.ibm.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