From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PULL] rtl8139 bugfix
Date: Tue, 08 May 2012 17:53:15 +0300 [thread overview]
Message-ID: <4FA9335B.3020301@redhat.com> (raw)
In-Reply-To: <4FA93265.8030605@codemonkey.ws>
On 05/08/2012 05:49 PM, Anthony Liguori wrote:
> On 05/08/2012 09:43 AM, Avi Kivity wrote:
>> On 05/08/2012 05:40 PM, Anthony Liguori wrote:
>>> On 05/08/2012 09:20 AM, Michael S. Tsirkin wrote:
>>>> The following changes since commit
>>>> 847c25d01cbe8e4fe457a7426f82daaaf3287aae:
>>>>
>>>> hw/ac97: Mask out the EAPD bit on Powerdown Ctrl/Stat writes
>>>> (2012-05-07 16:31:40 +0400)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
>>>>
>>>> for you to fetch changes up to
>>>> bdc62e62ead1a6c2a113934bf28cb5abef48618d:
>>>
>>> You need to use a tag/branch, not a commit.
>>>
>>> I don't know of a way to make git fetch all available objects in a
>>> repo.
>>>
>>
>> It's 'git fetch<remote>' (fetchs all reachable objects, not all
>> objects).
>
> That will just fetch based on your refspec. But without for an
> unnamed commit, i don't think there's a possible refspec that can
> describe all commits.
Right, it only works if a branch/tag was pushed.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-08 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 14:20 [Qemu-devel] [PULL] rtl8139 bugfix Michael S. Tsirkin
2012-05-08 14:39 ` Michael S. Tsirkin
2012-05-08 14:40 ` Anthony Liguori
2012-05-08 14:43 ` Avi Kivity
2012-05-08 14:49 ` Anthony Liguori
2012-05-08 14:53 ` Avi Kivity [this message]
2012-05-08 16:21 ` Paolo Bonzini
2012-05-08 14:55 ` Michael S. Tsirkin
2012-05-08 16:11 ` Anthony Liguori
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=4FA9335B.3020301@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.