public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW tools/lvmcmdline.c tools/vgsp ... Date: Thu, 15 Nov 2007 21:59:00 -0000 [thread overview] Message-ID: <20071115215911.9602.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2007-11-15 21:59:11 Modified files: . : WHATS_NEW tools : lvmcmdline.c vgsplit.c Log message: Fix --addtag to drop @ prefix from name Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.737&r2=1.738 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvmcmdline.c.diff?cvsroot=lvm2&r1=1.55&r2=1.56 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgsplit.c.diff?cvsroot=lvm2&r1=1.40&r2=1.41 --- LVM2/WHATS_NEW 2007/11/15 10:16:14 1.737 +++ LVM2/WHATS_NEW 2007/11/15 21:59:10 1.738 @@ -1,5 +1,6 @@ Version 2.02.29 - ================================== + Fix --addtag to drop @ prefix from name. Stop clvmd going haywire if a pre_function fails. Convert some vg_reads into vg_lock_and_reads. Avoid nested vg_reads when processing PVs in VGs and fix associated locking. --- LVM2/tools/lvmcmdline.c 2007/11/14 00:08:25 1.55 +++ LVM2/tools/lvmcmdline.c 2007/11/15 21:59:11 1.56 @@ -333,6 +333,8 @@ if (!validate_name(pos)) return 0; + a->value = pos; + return 1; } --- LVM2/tools/vgsplit.c 2007/11/15 02:53:49 1.40 +++ LVM2/tools/vgsplit.c 2007/11/15 21:59:11 1.41 @@ -243,6 +243,7 @@ if ((vg_to = vg_lock_and_read(cmd, vg_name_to, NULL, LCK_VG_WRITE | LCK_NONBLOCK, 0, 0))) { + /* FIXME Remove this restriction */ log_error("Volume group \"%s\" already exists", vg_name_to); unlock_vg(cmd, vg_name_from); return ECMD_FAILED;
reply other threads:[~2007-11-15 21:59 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=20071115215911.9602.qmail@sourceware.org \ --to=agk@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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).