From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: bzr check Date: Thu, 14 Jan 2010 13:40:28 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1263494448 32099 80.91.229.12 (14 Jan 2010 18:40:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Jan 2010 18:40:48 +0000 (UTC) Cc: Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 14 19:40:41 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NVUcZ-0006Tu-NA for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2010 19:40:40 +0100 Original-Received: from localhost ([127.0.0.1]:46718 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVUca-0006Eu-Da for ged-emacs-devel@m.gmane.org; Thu, 14 Jan 2010 13:40:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVUcV-0006Cc-8C for emacs-devel@gnu.org; Thu, 14 Jan 2010 13:40:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVUcQ-000651-LG for emacs-devel@gnu.org; Thu, 14 Jan 2010 13:40:34 -0500 Original-Received: from [199.232.76.173] (port=34590 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVUcQ-00064s-I6 for emacs-devel@gnu.org; Thu, 14 Jan 2010 13:40:30 -0500 Original-Received: from tomts20.bellnexxia.net ([209.226.175.74]:36292 helo=tomts20-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NVUcQ-0004KE-79 for emacs-devel@gnu.org; Thu, 14 Jan 2010 13:40:30 -0500 Original-Received: from toip4.srvr.bell.ca ([209.226.175.87]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20100114184029.FTSF27709.tomts20-srv.bellnexxia.net@toip4.srvr.bell.ca> for ; Thu, 14 Jan 2010 13:40:29 -0500 Original-Received: from bas1-montreal42-1178046351.dsl.bell.ca (HELO ceviche.home) ([70.55.143.143]) by toip4.srvr.bell.ca with ESMTP; 14 Jan 2010 14:01:28 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 0E08570035; Thu, 14 Jan 2010 13:40:28 -0500 (EST) In-Reply-To: (Juanma Barranquero's message of "Thu, 14 Jan 2010 18:27:21 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Solaris 8 (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:120025 Archived-At: >> I've never used it (in more than a year of use, maybe two), and since >> I don't think I'm an oddball user of Bazaar, I wouldn't fault the >> developpers if they spent 0 time on speeding up "bzr check". > IMO, bzr check is one of those commands that you don't use most of the > time, but when you do need it, you need it badly. Or are you saying > that checking the consistency of the repository is really never > needed? What do you propose when you suspect a failure, branching > again from upstream? How 'bout branching from the suspicious branch into a fresh new repository? It should rebuild the whole thing from scratch and hence fail if there's some corruption somewhere. Stefan