All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ned Bass <bass6@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [wc-discuss] Seeking contributors for Lustre User Manual
Date: Tue, 13 Nov 2012 10:33:02 -0800	[thread overview]
Message-ID: <20121113183302.GM31700@llnl.gov> (raw)
In-Reply-To: <CCC2E817.24EA%andreas.dilger@intel.com>

On Sat, Nov 10, 2012 at 12:09:09AM +0000, Dilger, Andreas wrote:
> The manual source is hosted in a Git/Gerrit repository in Docbook XML
> format and can be downloaded at:
> 
>     git clone http://git.whamcloud.com/doc/manual lustre-manual

That doesn't work for me:

  % git clone http://review.whamcloud.com/doc/manual  lustre-manual
  Cloning into lustre-manual...
  fatal: http://review.whamcloud.com/doc/manual/info/refs not found: did
    you run git update-server-info on the server?

I've only been able to check out the manual source directly from gerrit:

  git clone http://review.whamcloud.com/p/doc/manual lustre-manual

or,

  git clone ssh://nedbass at review.whamcloud.com:29418/doc/manual lustre-manual


Ned

  reply	other threads:[~2012-11-13 18:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F4644F70-E8BA-437F-87B1-9A57FADF8254@intel.com>
2012-11-10  0:09 ` [Lustre-devel] Seeking contributors for Lustre User Manual Dilger, Andreas
2012-11-13 18:33   ` Ned Bass [this message]
2012-11-13 19:48   ` [Lustre-devel] [wc-discuss] " Nathan Rutman
2012-11-13 21:26     ` Ned Bass
2012-11-13 21:43       ` Steven Jenkins
2012-11-14  3:21       ` Dilger, Andreas
2012-11-14 19:47       ` [Lustre-devel] Document Database Re: [Lustre-discuss] " Alex Kulyavtsev
2012-11-14 20:01         ` Richard P Wagner
2012-11-14 23:51       ` [Lustre-devel] " Christopher J. Walker
2012-11-15  0:12         ` Dilger, Andreas
2012-11-15  1:26           ` Ned Bass
2012-11-16 18:23             ` Henwood, Richard

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=20121113183302.GM31700@llnl.gov \
    --to=bass6@llnl.gov \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.