All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: FNST-Yang Hongyang <yanghy@cn.fujitsu.com>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/4] remus: move remus README to docs directory
Date: Wed, 25 Jun 2014 02:19:26 -0500	[thread overview]
Message-ID: <CAP8mzPPvEr4iTJsS6QNa9ZY-iLOtgoKsubOOc86MOucDTUn0PQ@mail.gmail.com> (raw)
In-Reply-To: <1403679610-26695-2-git-send-email-yanghy@cn.fujitsu.com>


[-- Attachment #1.1: Type: text/plain, Size: 1284 bytes --]

On Jun 25, 2014 12:34 PM, "Yang Hongyang" <yanghy@cn.fujitsu.com> wrote:
>
> We do not need a separate directory to store remus README, just
> move it to docs/ directory.
>
> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
> ---
>  docs/README.remus  | 4 ++++
>  tools/remus/README | 4 ----
>  2 files changed, 4 insertions(+), 4 deletions(-)
>  create mode 100644 docs/README.remus
>  delete mode 100644 tools/remus/README
>
> diff --git a/docs/README.remus b/docs/README.remus
> new file mode 100644
> index 0000000..9e8140b
> --- /dev/null
> +++ b/docs/README.remus
> @@ -0,0 +1,4 @@
> +Remus provides fault tolerance for virtual machines by sending continuous
> +checkpoints to a backup, which will activate if the target VM fails.
> +
> +See the website at http://nss.cs.ubc.ca/remus/ for details.
> diff --git a/tools/remus/README b/tools/remus/README
> deleted file mode 100644
> index 9e8140b..0000000
> --- a/tools/remus/README
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -Remus provides fault tolerance for virtual machines by sending continuous
> -checkpoints to a backup, which will activate if the target VM fails.
> -
> -See the website at http://nss.cs.ubc.ca/remus/ for details.
> --
> 1.9.1
>

Fine by me. But please do remove the nss.cs link as I mentioned in patch 3.

[-- Attachment #1.2: Type: text/html, Size: 1803 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-06-25  7:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  7:00 [PATCH 1/4] remus: remove old remus script Yang Hongyang
2014-06-25  7:00 ` [PATCH 2/4] remus: move remus README to docs directory Yang Hongyang
2014-06-25  7:19   ` Shriram Rajagopalan [this message]
2014-06-25  7:38     ` Hongyang Yang
2014-06-25  7:50       ` Shriram Rajagopalan
2014-06-30  5:56         ` Hongyang Yang
2014-06-30 17:05   ` Ian Jackson
2014-06-25  7:00 ` [PATCH 3/4] remus: add wikipage link to remus README Yang Hongyang
2014-06-25  7:14   ` Shriram Rajagopalan
2014-06-25  7:14     ` Hongyang Yang
2014-06-25  7:22       ` Shriram Rajagopalan
2014-06-30 17:05   ` Ian Jackson
2014-06-25  7:00 ` [PATCH 4/4] MAINTAINERS: Update maintained files of REMUS part Yang Hongyang
2014-06-30 17:06   ` Ian Jackson
2014-06-25  7:12 ` [PATCH 1/4] remus: remove old remus script Shriram Rajagopalan
2014-06-30 17:05 ` Ian Jackson

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=CAP8mzPPvEr4iTJsS6QNa9ZY-iLOtgoKsubOOc86MOucDTUn0PQ@mail.gmail.com \
    --to=rshriram@cs.ubc.ca \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.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 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.