xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian <murrayie@yahoo.co.uk>
To: xen-devel@lists.xen.org
Subject: Re: [Xen-users]  xen forum
Date: Tue, 21 May 2013 18:57:06 +0100	[thread overview]
Message-ID: <519BB572.1030009@yahoo.co.uk> (raw)
In-Reply-To: <1369152944.21246.106.camel@zakaz.uk.xensource.com>

On 21/05/13 17:15, Ian Campbell wrote:
> The process (send a signed-off-by email to xen-devel) hasn't changed 
> in forever. Some of the tools which are convenient (but not required) 
> to use have changed recently and therefore some of the advice might 
> have changed. 

I probably misunderstood the necessity, in that case.

> FWIW the answer is that .gitignore is wrong and using -f would have 
> been fine if you couldn't see where .gitignore was wrong (and fixing 
> .gitignore would have been fine if you could see where). 

Okay, thanks.
>>> Why would you expect to be more assured of a reply to your mails if a
>>> bug tracker had automatically logged them?
>> I am not assured of a reply, but surely the idea of a tracking system
>> is that bugs don't get forgotten about. In my case, I would have
>> raised an issue against xendomains, hopefully stated wants seems to go
>> wrong and either it sits there and is dealt with, batted back to me
>> for more info, or willfully ignored. But never should it just get
>> "lost in the cracks".
> Unfortunately without someone whose full time job it is to triage bugs
> and keep the bug tracker under control all of the bugs which get batted
> back and never followed up or which get ignored eventually overrun the
> system and make it useless for anyone who would actually want to use it.
> At this point you bug is just as likely to get lost in the mess as it is
> to get lost on xen-devel.
>
>> I'll shut up about it now, because whoever decides these things will
>> do what they want, anyway.
> We are working on a system which will allow us to record email threads
> as being relevant and useful to track. We believe this will suit our
> workflow better and avoid the need to have someone spend a lot of time
> bug wrangling on the track.

Ok, fair enough. We'll see :)


> This is why people are being encouraged to post their bugs to the list.

In hindsight, I think in the case of my xl/xendomains issue, it is 
better investigated as a bug as although I have a working patch, I don't 
fully understand why it's not an issue for other people and also my 
paych is probably not compatible with xm. So I'll post a bug report to 
the list with my work-around and hopefully somebody who understands the 
subject matter better can unpick the issue in a more authoritative manner.

Thanks for your time,

Ian.


>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2013-05-21 17:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 15:09 xen forum jacek burghardt
2013-05-19 15:16 ` Gordan Bobic
2013-05-19 16:36   ` Joseph Glanville
2013-05-19 17:04     ` Gordan Bobic
2013-05-21 14:29 ` Konrad Rzeszutek Wilk
2013-05-21 14:57   ` Gordan Bobic
2013-05-21 15:04     ` [Xen-users] " Ian Campbell
2013-05-22  6:18       ` Bartek Krawczyk
     [not found]       ` <CAFp_H4vqFyNN-ZPTo-C2rN6_j1DsXWWPugNM8du9Ssa+V1FHAQ@mail.gmail.com>
2013-05-22  6:55         ` Gordan Bobic
2013-05-22  9:53           ` Ian Campbell
2013-05-22  9:58             ` George Dunlap
2013-05-22 15:27               ` Gordan Bobic
2013-05-22 15:32                 ` George Dunlap
2013-05-22 15:52                   ` Gordan Bobic
2013-05-22 15:53                     ` Ian Campbell
2013-05-22 15:58                     ` George Dunlap
2013-05-22 20:54                     ` Gordan Bobic
2013-05-23 10:41                       ` George Dunlap
2013-05-23 12:04                         ` Ian Campbell
2013-05-23 13:08                           ` George Dunlap
2013-05-22 10:20           ` George Dunlap
2013-05-22 15:24             ` Gordan Bobic
2013-05-22 16:18               ` George Dunlap
2013-05-22 16:44                 ` Gordan Bobic
2013-05-23 13:40                   ` George Dunlap
2013-05-21 15:04   ` Ian Murray
2013-05-21 15:19     ` Ian Campbell
2013-05-21 16:00       ` Ian Murray
2013-05-21 16:15         ` Ian Campbell
2013-05-21 17:57           ` Ian [this message]
2013-05-21 16:31     ` Konrad Rzeszutek Wilk
2013-05-21 17:19       ` jacek burghardt
2013-05-21 18:03       ` Ian
2013-05-24 14:04       ` Konrad Rzeszutek Wilk
2013-05-24 19:37         ` Gordan Bobic
2013-05-24 21:36           ` Stefano Stabellini
2013-05-24 22:14             ` Gordan Bobic
2013-05-25 12:06               ` Konrad Rzeszutek Wilk
2013-05-28 16:00               ` George Dunlap
2013-05-25  3:07         ` Andrew Bobulsky
2013-05-28 13:49           ` Konrad Rzeszutek Wilk

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=519BB572.1030009@yahoo.co.uk \
    --to=murrayie@yahoo.co.uk \
    --cc=xen-devel@lists.xen.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).