All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: David F Barrera <dfbp@us.ibm.com>,
	xen-devel@lists.xensource.com, "Burns, Bill" <bburns@egenera.com>
Subject: Re: Is the repository broken?
Date: Fri, 21 Oct 2005 09:49:02 -0700	[thread overview]
Message-ID: <43591BFE.9030609@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017305A66C05@scsmsx402.amr.corp.intel.com>

Nakajima, Jun wrote:
> David F Barrera wrote:
> 
>>I saw the same thing. I just assumed that there had not been any
>>checkins since yesterday.
> 
> 
> This is basically what I memntioned in the previous email:
> 
> Nakajima, Jun wrote:
> 
>>I heard "the mini-regression test now in place between a staging tree
>>and the public tree currently fails on some 64bit SMP cases and
>>therefore all patches submitted after are still queued up in the
>>staging tree."
>>
>>I'm wondering how we can resolve that kind of situation effectively:
>>- Can we get the results from mini-regression tests?
>>- Can we access the staging tree to tell if the patch sent out has
>>been accepted or not? We need to reproduce the tree and problem to
>>fix the bug.
>>

Hello,

Is that what's going on? How can we help?

Is there a fifo operation in place? Can we perhaps remove
patches which fail and debug/process offline, perhaps post
to list and get testing, etc? Continue with regression
testing remaining queue?

thanks,
Nivedita

  reply	other threads:[~2005-10-21 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 16:41 Is the repository broken? Nakajima, Jun
2005-10-21 16:49 ` Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-21 19:14 Nakajima, Jun
2005-10-21 12:05 Burns, Bill
2005-10-21 16:18 ` David F Barrera

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=43591BFE.9030609@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=bburns@egenera.com \
    --cc=dfbp@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.