From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e52d2c3bb529d70ac17567a1b795f4a51a9b1467
Date: Thu, 22 May 2014 20:56:54 +0200 [thread overview]
Message-ID: <20140522185654.B111C20AD0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via e52d2c3bb529d70ac17567a1b795f4a51a9b1467 (commit)
from 61cf8114ea71d62fe953cd4a9d97e8a8ca8fbf30 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e52d2c3bb529d70ac17567a1b795f4a51a9b1467
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu May 22 20:56:10 2014 +0200
xen-image-maker: fix variable in README file.
-----------------------------------------------------------------------
Summary of changes:
config/xen-image/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/xen-image/README b/config/xen-image/README
index a59b6fa..5748121 100644
--- a/config/xen-image/README
+++ b/config/xen-image/README
@@ -20,5 +20,5 @@ other usefull commands from the Dom0:
- look what is going on: "xm top" or "xm list"
This script can also build a Citrix XenCenter xva image.
-- run "XEN_IMAGE_TYPE=xva sh xen-image-maker.sh" to build an xva image.
+- run "XEN_IMG_TYPE=xva sh xen-image-maker.sh" to build an xva image.
- import the vm with "xe vm-import file=ipfire.xfa"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-05-22 18:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140522185654.B111C20AD0@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox