public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/gnbd client/Makefile client/gnbd_monit ...
Date: Fri, 18 Mar 2005 19:39:00 -0000	[thread overview]
Message-ID: <20050318193939.22740.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	bmarzins@sourceware.org	2005-03-18 19:39:39

Modified files:
	gnbd/client    : Makefile gnbd_monitor.c gnbd_recvd.c 
	gnbd/man       : fence_gnbd.8 gnbd.8 gnbd_export.8 gnbd_import.8 
	gnbd/server    : Makefile device.c gnbd_serv.c local_req.h 
	gnbd/tools/gnbd_export: Makefile 
	gnbd/tools/gnbd_import: Makefile gnbd_import.c 
	gnbd/utils     : gnbd_utils.c gnbd_utils.h 

Log message:
	Syncing head with RHEL4 branch.
	Added fix for 151321. gnbd now defaults to getting the node name from the
	cluster manager
	Added Bastian Blanks patchs to the man pages

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/client/Makefile.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/client/gnbd_monitor.c.diff?cvsroot=cluster&r1=1.6&r2=1.7
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/client/gnbd_recvd.c.diff?cvsroot=cluster&r1=1.4&r2=1.5
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/man/fence_gnbd.8.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/man/gnbd.8.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/man/gnbd_export.8.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/man/gnbd_import.8.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/Makefile.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/device.c.diff?cvsroot=cluster&r1=1.4&r2=1.5
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/gnbd_serv.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/local_req.h.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/tools/gnbd_export/Makefile.diff?cvsroot=cluster&r1=1.1&r2=1.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/tools/gnbd_import/Makefile.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/tools/gnbd_import/gnbd_import.c.diff?cvsroot=cluster&r1=1.11&r2=1.12
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/utils/gnbd_utils.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/utils/gnbd_utils.h.diff?cvsroot=cluster&r1=1.3&r2=1.4


             reply	other threads:[~2005-03-18 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18 19:39 bmarzins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-13 22:32 bmarzins
2005-03-16 22:40 bmarzins

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=20050318193939.22740.qmail@sourceware.org \
    --to=bmarzins@sourceware.org \
    --cc=cluster-cvs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).