Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iAEKQXOs002076 for ; Sun, 14 Nov 2004 20:26:34 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id 039A854798 for ; Sun, 14 Nov 2004 20:26:37 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CTR5y-0007Qx-8f for migo@homemail.com; Sun, 14 Nov 2004 15:35:34 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CTR5P-0007Qo-CY for gnu-arch-users@gnu.org; Sun, 14 Nov 2004 15:34:59 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CTR5P-0007Qc-03 for gnu-arch-users@gnu.org; Sun, 14 Nov 2004 15:34:59 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CTR5O-0007QZ-Tz for gnu-arch-users@gnu.org; Sun, 14 Nov 2004 15:34:58 -0500 Received: from [129.255.60.186] (helo=ct.radiology.uiowa.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CTQwb-00034O-FY for gnu-arch-users@gnu.org; Sun, 14 Nov 2004 15:25:53 -0500 Received: from [192.168.1.11] (12-217-241-0.client.mchsi.com [12.217.241.0]) by ct.radiology.uiowa.edu (8.11.6/8.11.6) with ESMTP id iAEKPo325093; Sun, 14 Nov 2004 14:25:51 -0600 Message-ID: <4197BF40.1010300@arbash-meinel.com> Date: Sun, 14 Nov 2004 14:25:36 -0600 From: John Meinel User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Karl O. Pinc" Subject: Re: [Gnu-arch-users] Removing the last changeset(s) from the archive References: <20041114111431.E15533@mofo.meme.com> <4197AAA5.7080501@panoramicfeedback.com> <20041114131902.Q15533@mofo.meme.com> <1100459623.15201.46.camel@localhost> <20041114134530.A23046@mofo.meme.com> In-Reply-To: <20041114134530.A23046@mofo.meme.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Cc: gnu-arch-users@gnu.org, Charles Duffy X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0652056829==" Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 3408 Lines: 97 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0652056829== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0F075DE81DFA1F53F76CAE4E" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0F075DE81DFA1F53F76CAE4E Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Karl O. Pinc wrote: [...] > > Maybe that's what I should mean. In general I just go on and > finish fixing whatever I was working on (the larger problem) > and commit when I get that working and then the archive again > has a working revision. > > Reverse/sync-tree/commit looks like it would be the right way to keep > the latest revision in the archive 'working' as often as possible. > > That the moment my archive is not shared so I don't care whether the > latest revision works all the time or not. My thoughts are that > it'd be nice to be able to keep an archive where _all_ the > revisions work, which leads me to want to 'un-commit'. Although > it's not exactly true that I want the trees in the archive to > work. It's more like I want them to be mental checkpoints. > Done with this part, check. Done with that, check. Goofing > up a commit violates this mental model. > > Karl > Free Software: "You don't pay back, you pay forward." > -- Robert A. Heinlein > I think you've just described the difference between a dev tree, and a stable tree. Committing to a stable tree should involve quite a bit of thought, and checking to make sure everything is correct. For me, a dev tree is just that. Something where I'm doing development, and don't even make the guarantee that it will compile. I might be a little unique in this, since I tend to work from multiple machines, and I use revision control to move between them (used to use CVS, now arch). So frequently not only are my programs broken, but they won't even compile. But that's why there is a dev branch, and a mainline/stable branch. For a lot of my stuff, there is only a dev branch, because it's not worth the overhead of stable if I'm the only one using it. But if you really want "this tree is always good", you probably want something more like a stable branch, rather than trying to do that with your dev branch. arch makes creating and maintaining concurrent branches very easy. Might as well put that to good use. John =:-> --------------enig0F075DE81DFA1F53F76CAE4E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBl79CJdeBCYSNAAMRAks9AJ9l6kAZ+MYBOUwSFbEKz27DBQ9KCACfRZLa nl5cNKc8Kdv3/ASBvoLBgRo= =HapB -----END PGP SIGNATURE----- --------------enig0F075DE81DFA1F53F76CAE4E-- --===============0652056829== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ --===============0652056829==--