From: malc <av1474@comtv.ru>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: commits not reported to qmu-commits?
Date: Sun, 4 Oct 2009 19:03:26 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0910041901570.2140@linmac.oyster.ru> (raw)
In-Reply-To: <20091004114152.GA17081@redhat.com>
On Sun, 4 Oct 2009, Michael S. Tsirkin wrote:
> On Sun, Oct 04, 2009 at 03:30:39PM +0400, malc wrote:
> > On Sun, 4 Oct 2009, Michael S. Tsirkin wrote:
> >
> > > On Sun, Oct 04, 2009 at 01:45:54PM +0400, malc wrote:
> > > > On Sun, 4 Oct 2009, Michael S. Tsirkin wrote:
> > > >
> > > > > Hi,
> > > > > I'm subscribed to qmu-commits list. but I didn't get
> > > > > mail about these commits:
> > > > > commit c227f0995e1722a1abccc28cadf0664266bd8043
> > > > > commit 99a0949b720a0936da2052cb9a46db04ffc6db29
> > > > > Is this a problem on my side? Did others get it?
> > > >
> > > > Largeish commits are silently dropped.
> > >
> > > By whom?
> >
> > I have no idea, if i had to guess, my guess would be - a robot.
>
> If savannah is doing this, let's just set up another list somewhere?
> commit lists are easy, we can have as many as we like.
I don't know how many subscribers qemu-commits has, at least 3, now
multiply that by 1.6Mb those two patches alone would have generated
per subscriber and thing again whether it's a good idea.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-10-04 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 9:40 [Qemu-devel] commits not reported to qmu-commits? Michael S. Tsirkin
2009-10-04 9:45 ` [Qemu-devel] " malc
2009-10-04 11:11 ` Michael S. Tsirkin
2009-10-04 11:30 ` malc
2009-10-04 11:41 ` Michael S. Tsirkin
2009-10-04 15:03 ` malc [this message]
2009-10-04 15:26 ` Michael S. Tsirkin
2009-10-04 17:52 ` malc
2009-10-06 9:53 ` Michael S. Tsirkin
2009-10-06 9:27 ` Amit Shah
2009-10-04 19:21 ` Anthony Liguori
[not found] ` <m3r5thekf1.fsf@neno.mitica>
2009-10-05 19:54 ` Michael S. Tsirkin
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=Pine.LNX.4.64.0910041901570.2140@linmac.oyster.ru \
--to=av1474@comtv.ru \
--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 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).