From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22702 invoked by alias); 13 Dec 2012 16:13:18 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30882 Received: (qmail 29357 invoked from network); 13 Dec 2012 16:13:16 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-b7fd76d000007247-8c-50c9fe989bf7 Date: Thu, 13 Dec 2012 16:13:11 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Access to CVS Message-id: <20121213161311.27ca1cfc@pwslap01u.europe.root.pri> In-reply-to: <12941.1355403532@thecus.kiddle.eu> References: <20121204225059.GA9935@redoubt.spodhuis.org> <26711.1354667636@thecus.kiddle.eu> <20121205031447.GA26262@redoubt.spodhuis.org> <121205014000.ZM22819@torch.brasslantern.com> <20121205112647.GA34241@redoubt.spodhuis.org> <20121205195013.64ef36c0@pws-pc.ntlworld.com> <20121207000521.GD20703@pug.qqx.org> <20121207094935.0d9bce83@pwslap01u.europe.root.pri> <4810.1355267148@thecus.kiddle.eu> <87a9tjwuec.fsf@ft.bewatermyfriend.org> <8272.1355333127@thecus.kiddle.eu> <121212105719.ZM28299@torch.brasslantern.com> <12941.1355403532@thecus.kiddle.eu> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42I5/e/4Zd0Z/04GGJxbxWpxsPkhkwOjx6qD H5gCGKO4bFJSczLLUov07RK4Mu527GctmMFece/BMdYGxpusXYycHBICJhLTdt9nhrDFJC7c W8/WxcjFISSwlFHiyp7FbCAJIYHlTBLvZwmC2CwCqhJfmi+CNbMJGEpM3TSbEcQWERCXOLv2 PEsXIweHsICUxPrtPCBhXgF7iX1TVoGVcAoYSOz8NZMdYn4Pq8SFm9vYQRL8AvoSV/9+YoI4 wl5i5pUzjBDNghI/Jt9jAbGZBbQkNm9rYoWw5SU2r3nLPIFRYBaSsllIymYhKVvAyLyKUTS1 NLmgOCk910ivODG3uDQvXS85P3cTIyQEv+5gXHrM6hCjAAejEg9vYfjJACHWxLLiytxDjBIc zEoivDdeA4V4UxIrq1KL8uOLSnNSiw8xMnFwSjUwCrekf//SXpzU56iwc0Hbx+cvjI4x3aq+ Oaf81By5vaEnvLctmekz6+zK6QsvB/+Kef0416xXSGQTx8K1K7gCTObLspwIcGtTn95Vqc3D EHnwa2tW+gJGNfuMHTrTD09Qu/jdsOPxhsuO3NYa4nIaos+V936u/mV97MqbowUas6ufdL9f tSp8qhJLcUaioRZzUXEiABIIq/kfAgAA On Thu, 13 Dec 2012 13:58:52 +0100 Oliver Kiddle wrote: > Bart wrote: > > I would greatly appreciate it if someone would generate a summary > > of the conclusions of this discussion with all the various > > "recommended" steps that one would perform, so that it could be > > added as a sort of how-to in Etc/zsh-development-guide. > > Ok, how does this look? Probably OK, although I don't understand all the words. It might be useful to give a sample list of explicit git commands to use at each stage, in particular what you'd do for an initial commit, for updating the commit with the mailing list ID, for any kind of trickery to reduce the number of commits that get pushed, and for pushing it back (as this is for those new to git you can assume the relationship between the local archive and the remote master is simple and let the git gurus do the clever stuff). pws