From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MTrXk-0004IH-BY for garchives@archives.gentoo.org; Thu, 23 Jul 2009 06:12:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1583DE0212; Thu, 23 Jul 2009 06:12:39 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id EB339E0212 for ; Thu, 23 Jul 2009 06:12:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 8139F66B0D for ; Thu, 23 Jul 2009 06:12:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.996 X-Spam-Level: X-Spam-Status: No, score=-2.996 required=5.5 tests=[AWL=0.603, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGT4VAFj3-fm for ; Thu, 23 Jul 2009 06:12:32 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 92C8F6535E for ; Thu, 23 Jul 2009 06:12:30 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MTrXW-00065R-46 for gentoo-dev@gentoo.org; Thu, 23 Jul 2009 06:12:26 +0000 Received: from ip68-231-21-207.ph.ph.cox.net ([68.231.21.207]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 23 Jul 2009 06:12:26 +0000 Received: from 1i5t5.duncan by ip68-231-21-207.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 23 Jul 2009 06:12:26 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: Progress on Universal Select Tool Date: Thu, 23 Jul 2009 06:12:15 +0000 (UTC) Message-ID: References: <1245163715.14589.515.camel@thedude> <1248288117.7494.34.camel@thedude> <8b4c83ad0907222009sba2c36fu59d2caf68ebcfd95@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-21-207.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Cc: gentoo-soc@lists.gentoo.org Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 10c2b9db-655d-454f-beac-ff0ac38972c4 X-Archives-Hash: 9aa02ee50bd792221d8b87d2fdbc60b1 Nirbheek Chauhan posted 8b4c83ad0907222009sba2c36fu59d2caf68ebcfd95@mail.gmail.com, excerpted below, on Thu, 23 Jul 2009 08:39:00 +0530: > 2009/7/23 S=C3=A9rgio Almeida: >> I'm still not doing any commits as uselect can still break your python >> environment while testing and i don't have the time to learn how to >> handle branches in git. > It's probably wise to commit code in small-ish (and self-containing) > discrete units each of which add something without breaking anything. > Otherwise, it becomes very difficult to track down which change broke > something via git bisect. I would recommend that you try to do this, if > only just to learn how to make good commits. >=20 > You could take a look at how the kernel folks handle this -- features g= o > in as several small commits/patches. As a non-dev direct git kernel tester and bug filer that now regularly=20 bisects new bugs I find down to the individual commit, absolutely 100%=20 agreed. It's SO much easier for even a non-dev to properly test and=20 bisect a properly commit unitized git source, than it was to do it=20 manually, before, and the quality of my bugs and the resolutions thereof=20 well demonstrate that fact. While git branches are FWIW trivial, if you don't want to deal with them=20 ATM, don't. Just get the unitary commits right, and use tagging to=20 demarcate points where you believe it's stable enough to test. The rest=20 will come, in time. (Again, I say this as a non-dev, but even tho I'm=20 not a dev and don't fully understand git myself, in git, branching=20 really /is/ trivial, even for non-dev testers. =3D:^) --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman