From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Subject: Re: [Xen-users] xen forum Date: Tue, 21 May 2013 18:57:06 +0100 Message-ID: <519BB572.1030009@yahoo.co.uk> References: <20130521142917.GO492@phenom.dumpdata.com> <1369148649.60268.YahooMailNeo@web171304.mail.ir2.yahoo.com> <1369149573.21246.100.camel@zakaz.uk.xensource.com> <1369152043.6482.YahooMailNeo@web171303.mail.ir2.yahoo.com> <1369152944.21246.106.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1369152944.21246.106.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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