From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2a6f6b679d06acf2c280c4887d231330@quanstro.net> To: 9fans@9fans.net From: erik quanstrom Date: Thu, 25 Dec 2008 09:37:09 -0500 In-Reply-To: <65ACAFFD-2186-450E-8C1B-D5FDC1699F46@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] Changelogs & Patches? Topicbox-Message-UUID: 7065782a-ead4-11e9-9d60-3106f5b1d025 > I surely hope the festive mood of the season will protect me from being > ostracized for asking this, but is there any chance to map Plan9 > development practices to some of the established ways of source > code management? I mostly long for things like being able to browse > Plan9 history with a clear understanding of who did what and for > what reason. in the holiday spirit ☺, isn't this similar logic 1 scm packages are peace hope and light, everybody knows that. 2. if you don't use a scum package you are in the darkness 3. if you are in the darkness, you must be saved, or be cast into the pit. despite the season, and typical attitudes, i don't think that development practices are a spiritual or moral decision. they are a practical one. and what they have done at the labs appears to be working to me. in my own experience, i've found scum always to cost time. but my big objection is the automatic merge. automatic merges make it way too easy to merge bad code without reviewing the diffs. while a descriptive history is good, it takes a lot of extra work to generate. just because it's part of the scum process doesn't make it free. - erik