Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!goblin3!goblin2!goblin.stu.neva.ru!newsfeed1.swip.net!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.013 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'repository': 0.05; '(b)': 0.07; '21,': 0.07; 'restarting': 0.07; 'subject:Question': 0.07; 'git': 0.09; 'subject:Source': 0.09; 'cc:addr:python-list': 0.11; 'project,': 0.12; 'assume': 0.14; 'changes': 0.15; "'size'": 0.16; '(it': 0.16; 'cares': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'personally,': 0.16; 'prospect': 0.16; 'stuff,': 0.16; 'wrote:': 0.18; 'else,': 0.19; 'command': 0.22; 'code,': 0.22; 'coding': 0.22; 'cc:addr:python.org': 0.22; '(a)': 0.24; 'cc:2**0': 0.24; 'right.': 0.26; 'header:In-Reply- To:1': 0.27; 'message-id:@mail.gmail.com': 0.30; 'concern': 0.31; 'own,': 0.31; 'anyone': 0.31; 'there.': 0.32; 'run': 0.32; 'everyone': 0.33; 'fri,': 0.33; "i'd": 0.34; 'created': 0.35; 'problem.': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'version': 0.36; 'done': 0.36; 'should': 0.36; 'easiest': 0.38; 'stable': 0.38; 'version,': 0.38; 'whatever': 0.38; 'pm,': 0.38; 'recent': 0.39; 'does': 0.39; 'how': 0.40; 'collaborate': 0.60; 'worry': 0.60; 'most': 0.60; 'helps': 0.61; 'full': 0.61; "you're": 0.61; 'such': 0.63; 'interest': 0.64; 'size.': 0.65; 'latest': 0.67; 'mar': 0.68; 'frank': 0.68; 'wish': 0.70; 'subject:Control': 0.84; 'adopt': 0.91; 'download.': 0.91; 'to:none': 0.92; 'wishing': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=EkahZwXSrx8dsTsxfnYhbymPMaV/e1rzedYSsK7F9fM=; b=zxL4K4EcWRoIOlWaTV6vJYHErm8YKfq5WgxxnGnf8WZUSTodvhH7NamvU6mVr7i9Qb oZZbLZL7aln77RPJAJSmH1jPBJwm0mUCXJ/WMJjhVeqnSCpLzC9merPNln2E1A8T+xF1 e7ibsmw02Icm2Ah5VdrqgyKTa4Ok4elUbkRFhR+OgCq6/pbUf/bnRdbRX06itpEsF8Jo /l43OgBCIBNFjK31l8nrfnP+M4se2vdAbIDVR+cXGdzQ1RYIqUorBobgm+8tGtKuD//8 fRNuVkwh61NxJmZx0SN3zE2Tkfpo1IpJQayLJG8i0V366ezhMEdwPnYsJ9Pyd/adQssn 4kdQ== MIME-Version: 1.0 X-Received: by 10.68.215.40 with SMTP id of8mr50912308pbc.15.1395380827693; Thu, 20 Mar 2014 22:47:07 -0700 (PDT) In-Reply-To: References: <20140321013313.GA58343@cskk.homeip.net> Date: Fri, 21 Mar 2014 16:47:07 +1100 Subject: Re: Question about Source Control From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 32 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1395380837 news.xs4all.nl 2900 [2001:888:2000:d::a6]:39749 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:68674 On Fri, Mar 21, 2014 at 4:40 PM, Frank Millman wrote: > To make the software available to anyone who just wants to run a stable > version, copy the working directory of the 'major release' repository to a > directory of its own, without the .hg stuff, and make it available for > download. > > For everyone else, just make the full repository available, and don't worry > about the size. > > 'Everyone else' would include those wishing to collaborate on the project, > and those who just wish to keep up to date with the latest updates. That sounds about right. I have a number of people who use Gypsum without any interest in coding it, but cloning the git repo is still the easiest way to (a) get the code, and (b) pull changes later. (It helps that I created a command in the program that pulls changes and then does an internal "update all" to apply those changes without restarting the program.) > Actually my concern was not the 'size' of the full repository, but the > prospect of wading through thousands of changesets most of which are ancient > history. However, I assume that the experienced user will adopt habits such > as 'hg log tip:-10' to review the last 10 changesets, so it should not be a > problem. Anyone who actually cares about the changes will need to know how to use the version control system you're using. They can then use "hg view" or "hg log" or whatever to see just what they care about; personally, I'd just use "hg log|less", which is like "git log" - when you're done reading recent stuff, hit q and get out of there. ChrisA