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: Emacs 23.1.90 pretest Date: Wed, 09 Dec 2009 16:18:04 -0500 Message-ID: References: <87r5r47t7p.fsf@stupidchicken.com> <87y6lcqkpn.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1260393507 16623 80.91.229.12 (9 Dec 2009 21:18:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Dec 2009 21:18:27 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 09 22:18:19 2009 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 1NITvN-0006En-7y for ged-emacs-devel@m.gmane.org; Wed, 09 Dec 2009 22:18:17 +0100 Original-Received: from localhost ([127.0.0.1]:41361 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NITvM-0003Ir-Rd for ged-emacs-devel@m.gmane.org; Wed, 09 Dec 2009 16:18:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NITvG-0003Fn-6f for emacs-devel@gnu.org; Wed, 09 Dec 2009 16:18:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NITvB-00039J-Rq for emacs-devel@gnu.org; Wed, 09 Dec 2009 16:18:09 -0500 Original-Received: from [199.232.76.173] (port=33229 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NITvB-000398-Hm for emacs-devel@gnu.org; Wed, 09 Dec 2009 16:18:05 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:38358 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NITvB-0008Eq-9F for emacs-devel@gnu.org; Wed, 09 Dec 2009 16:18:05 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEABOjH0vO+INN/2dsb2JhbACBTNVJhCwEihs X-IronPort-AV: E=Sophos;i="4.47,370,1257138000"; d="scan'208";a="51131576" Original-Received: from 206-248-131-77.dsl.teksavvy.com (HELO pastel.home) ([206.248.131.77]) by ironport2-out.pppoe.ca with ESMTP; 09 Dec 2009 16:18:04 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 5CCA08065; Wed, 9 Dec 2009 16:18:04 -0500 (EST) In-Reply-To: (Andreas Schwab's message of "Wed, 09 Dec 2009 21:07:22 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:118486 Archived-At: >>>> Unfortunately, this kind of thing tends to happen in first pretests when >>>> people try to squeeze stuff in at the last minute as I'm rolling the >>>> tarball. >>> You can avoid that if you use cvs rtag. >> I thought rtag was the problematic one. I always use `tag' instead, so >> I know it tags exactly the files I'm seeing at the moment. > The right way is to use rtag, then do a fresh checkout of that tag. > That's the only way to guarantee a consistent tag. "consistent" in which sense? >> Then you can use that tag to export those exact same files to build a >> tarball, no matter what else happens on the trunk in the mean time. > As you can see with the EMACS_PRETEST_23_1_90 tag, this can result in > the wrong revisions to be tagged. I really can't imagine why "tag" would be a problem. "tag" is suppose to tag exactly the revisions of the files you have currently checked out, so if those files are fine, so is your tag. Luckily, I soon won't have to worry about such CVS idiosyncrasies any more. > As a result the git tree is unable to accurately represent that tag. I can definitely imagine lots of cases where it might be very difficult to represent tags properly when translating from CVS to something else, regardless of how the tag was applied. Stefan