From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v7 2/2] qemu-ga: sample fsfreeze hooks
Date: Fri, 7 Dec 2012 16:31:13 -0200 [thread overview]
Message-ID: <20121207163113.2f238c8f@doriath.home> (raw)
In-Reply-To: <50C233FE.5020904@redhat.com>
On Fri, 07 Dec 2012 11:22:54 -0700
Eric Blake <eblake@redhat.com> wrote:
> On 12/07/2012 06:55 AM, Luiz Capitulino wrote:
> > On Fri, 07 Dec 2012 17:39:32 +0900
> > Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com> wrote:
> >
> >> Adds sample hook scripts for --fsfreeze-hook option of qemu-ga.
> >> - fsfreeze-hook : execute scripts in fsfreeze-hook.d/
> >> - fsfreeze-hook.d/mysql-flush.sh.sample : quiesce MySQL before snapshot
> >>
> >> Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
> >> ---
> >> .gitignore | 1
> >> Makefile | 2 -
> >> scripts/qemu-guest-agent/fsfreeze-hook | 33 ++++++++++++
> >> .../fsfreeze-hook.d/mysql-flush.sh.sample | 55 ++++++++++++++++++++
> >> 4 files changed, 90 insertions(+), 1 deletion(-)
> >> create mode 100755 scripts/qemu-guest-agent/fsfreeze-hook
> >> create mode 100755 scripts/qemu-guest-agent/fsfreeze-hook.d/mysql-flush.sh.sample
> >>
> >> diff --git a/.gitignore b/.gitignore
> >> index bd6ba1c..286822d 100644
> >> --- a/.gitignore
> >> +++ b/.gitignore
> >> @@ -93,3 +93,4 @@ cscope.*
> >> tags
> >> TAGS
> >> *~
> >> +!scripts/qemu-guest-agent/fsfreeze-hook.d
> >
> > Why? Do we expect to have *~ files in there?
>
> What does your question have to do with the patch, which isn't even
> touching the pre-existing *~ line?
As far I could understand the ! prefix in gitignore documention, it's
changing the *~ meaning for the fsfreeze-hoo.d directory, and I wanted
to understand why.
> >> diff --git a/Makefile b/Makefile
> >> index 9ecbcbb..466dcd7 100644
> >> --- a/Makefile
> >> +++ b/Makefile
> >> @@ -248,7 +248,7 @@ clean:
> >> # avoid old build problems by removing potentially incorrect old files
> >> rm -f config.mak op-i386.h opc-i386.h gen-op-i386.h op-arm.h opc-arm.h gen-op-arm.h
> >> rm -f qemu-options.def
> >> - find . -name '*.[od]' -exec rm -f {} +
> >> + find . -name '*.[od]' -type f -exec rm -f {} +
> >
> > What does this change have to do with this patch?
>
> Because this patch introduces a directory
> scripts/qemu-guest-agent/fsfreeze-hook.d/mysql-flush.sh.sample that
> belongs to the repo and therefore must not be cleaned.
next prev parent reply other threads:[~2012-12-07 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 8:39 [Qemu-devel] [PATCH v7 0/2] qemu-ga: add hook to quiesce the guest on fsfreeze-freeze/thaw Tomoki Sekiyama
2012-12-07 8:39 ` [Qemu-devel] [PATCH v7 1/2] qemu-ga: execute " Tomoki Sekiyama
2012-12-07 13:52 ` Luiz Capitulino
2012-12-07 8:39 ` [Qemu-devel] [PATCH v7 2/2] qemu-ga: sample fsfreeze hooks Tomoki Sekiyama
2012-12-07 13:55 ` Luiz Capitulino
2012-12-07 17:47 ` mdroth
2012-12-07 18:29 ` Luiz Capitulino
2012-12-07 18:22 ` Eric Blake
2012-12-07 18:31 ` Luiz Capitulino [this message]
2012-12-07 18:37 ` Eric Blake
2012-12-07 18:57 ` Luiz Capitulino
2012-12-10 6:23 ` Tomoki Sekiyama
2012-12-07 18:34 ` Eric Blake
2012-12-10 6:23 ` Tomoki Sekiyama
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=20121207163113.2f238c8f@doriath.home \
--to=lcapitulino@redhat.com \
--cc=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=tomoki.sekiyama.qu@hitachi.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 NNTP newsgroup(s).