Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Florian Haas <florian@hastexo.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] User's Guide fix for variable-rate sync; missing doc in man pages
Date: Fri, 11 Nov 2011 16:26:36 +0100	[thread overview]
Message-ID: <4EBD3EAC.2020803@hastexo.com> (raw)
In-Reply-To: <4EBD3BF7.9020406@hastexo.com>

On 2011-11-11 16:15, Florian Haas wrote:
> Phil/Lars,

Actually, please pull the following two minor changes as well (been
meaning to do this for a while; never got around to doing it):

Florian Haas (2):
      User's Guide: add joint copyright notice for hastexo
      User's Guide: update blog links in "more info" section

 users-guide/drbd-users-guide-docinfo.xml |    4 ++++
 users-guide/more-info.txt                |    7 +++----
 2 files changed, 7 insertions(+), 4 deletions(-)

All available from the same location,
git://github.com/fghaas/drbd-documentation master

Thanks!

Cheers,
Florian

      parent reply	other threads:[~2011-11-11 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 15:15 [Drbd-dev] User's Guide fix for variable-rate sync; missing doc in man pages Florian Haas
2011-11-11 15:20 ` Andrea Spadaccini
2011-11-11 15:26 ` Florian Haas [this message]

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=4EBD3EAC.2020803@hastexo.com \
    --to=florian@hastexo.com \
    --cc=drbd-dev@lists.linbit.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