From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13505 invoked by alias); 15 Dec 2012 19:13:44 -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: 30892 Received: (qmail 7193 invoked from network); 15 Dec 2012 19:13:31 -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=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, HTML_MESSAGE,RCVD_IN_DNSWL_LOW,T_DKIM_INVALID autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.171 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=R9WMgA92XQcXN0Zw4/4xIta5/PWHt/nBAgS8L+4Ty1w=; b=mQsxI+3g6Z6GgIXY0dfeXdgJ6f3s2veA/R4y+b38HALfJZDfUsF5Z/6ZF1vOCCb2Kt P3ra3aCuzwA8uIuMoWjZusXzxB22Kd0TjpdshhPBacDx/0t3hrF7CwcE844VD2o9EPL8 ezI1It/R1N04EqoCiRmR6o+XXTBaCTsRHcpSSQIR2nOYCnIC6yAxrQzGhRbcZavdxTeK eqkw04MIZnH0/hzxAE+ylMrGW9EonYhv1zuq0rtJu4+lrglYf/rmoTcobfdnbP11cqFY Or857SCddJb/C/bJY0GxEloAHorT46J+Ukvhm3HW00VFi+nGHrBjGYwP4EYvOV+zfc+z BhAw== MIME-Version: 1.0 Sender: 4wayned@gmail.com In-Reply-To: <20121215180934.65918de9@pws-pc.ntlworld.com> References: <17903.1355496262@thecus.kiddle.eu> <20121214150912.03bde6ae@pwslap01u.europe.root.pri> <20121214192945.GA40810@redoubt.spodhuis.org> <20121215180934.65918de9@pws-pc.ntlworld.com> Date: Sat, 15 Dec 2012 11:07:37 -0800 X-Google-Sender-Auth: 8wu4i6RYAOLD6TlBXHEa9VKQrtc Message-ID: Subject: Re: Access to CVS From: Wayne Davison To: Peter Stephenson Cc: Phil Pennock , Zsh workers Content-Type: multipart/alternative; boundary=f46d04083865823db104d0e8dc8a --f46d04083865823db104d0e8dc8a Content-Type: text/plain; charset=UTF-8 On Sat, Dec 15, 2012 at 10:09 AM, Peter Stephenson < p.w.stephenson@ntlworld.com> wrote: > If anybody thinks that above *isn't* the basic sequence, or that their > own preferred procedure is something other than a more sophisticated > form of theabove, it would be good to hear. > It's always good to view your own commit to double-check it, and to also to check for missed files. So I'd suggest adding "git show" after "git commit -a" (that lets you look over your latest commit) and "git status" (lets you look for uncommitted files). And then, right before the "git push", toss in "git pull --rebase" to remind folks to check for remote changes prior to pushing (using --rebase instead of merge). Finally, it would be good to mention tags somewhere, since it requires a separate "git push --tags" if you want your tags to become public, but I doubt we'd want to mention it in the basic sequence, since it's likely we just want things like release tags. % $VISUAL file1.c file2.c new-file3.c % git add new-file3.c % git commit -a % git show % git status % git pull --rebase % git push ..wayne.. --f46d04083865823db104d0e8dc8a--