qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
To: lcapitulino@redhat.com
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v7 2/2] qemu-ga: sample fsfreeze hooks
Date: Mon, 10 Dec 2012 15:23:28 +0900	[thread overview]
Message-ID: <50C57FE0.3020502@hitachi.com> (raw)
In-Reply-To: <20121207165748.0bf3b55e@doriath.home>

Hi, sorry for my late reply.

On 2012/12/08 3:57, Luiz Capitulino wrote:
> On Fri, 07 Dec 2012 11:37:44 -0700
> Eric Blake <eblake@redhat.com> wrote:
> 
>> On 12/07/2012 11:31 AM, Luiz Capitulino wrote:
>>>>>> +++ 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.
>>>
>>
>> No, it is changing a much earlier line:
>>
>> *.d
>>
>> to say that this _particular_ .d is allowed to be committed.  It has
>> nothing to do with *~.

Yes, it's for adding fsfreeze-hook.d into the repo.

> Ah, now it makes a lot of sense, thanks Eric.
> 
> It would be nice to move it right below *.d, to avoid stupid comments :)

And OK, I will move this there.

>> Still, I have to wonder if we really want to store these files in a .d
>> in the repository itself, or if we should store them under some other
>> file name and only at 'make install' time insert them into a .d at the
>> install destination.  It would clean up this confusion about the
>> .gitignore as well as the change to the 'find' command during 'make clean'.
> 
> Well, now that I understand it both ways are fine with me (ie. what you
> suggest and what's been implemented in this patch).
Then I'd like to keep current implementation.

Thanks,
-- 
Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory

  reply	other threads:[~2012-12-10  6:22 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
2012-12-07 18:37         ` Eric Blake
2012-12-07 18:57           ` Luiz Capitulino
2012-12-10  6:23             ` Tomoki Sekiyama [this message]
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=50C57FE0.3020502@hitachi.com \
    --to=tomoki.sekiyama.qu@hitachi.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).