From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4399 invoked by alias); 30 Jul 2013 20:45:09 -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: 31624 Received: (qmail 6992 invoked from network); 30 Jul 2013 20:45:05 -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.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.43 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 :content-transfer-encoding; bh=JVouOqecZisoka2Ew8JQRPb5IExvm4bYqxRY684kslE=; b=mT+bngq+qIgDnx9PNKySmMGSjdSltggskay3bJCR+0g1Vpl/5GS52GFfoR2WnzjplL XQd6l7rZ8X46ZYz8cVXBYrAG1hF5OMgamlG9ZmWiwerYmDaWLGIJr3IbJ0mRn2e1sg5V jbjBT6pId0mrH4GbNCAV9DEPwfv7V+NNTZmg/ziH52mGdoUViptA5irWESqcaMfjcWiu aQNizSsCdnvK/rFefy0nUXksUL9f/Wyqb2WxBHxCrpYGe3RYiKVjd1+rILUE+4aw51Mc /iZayTGzPBeFjQrw8a4vLsCN8lsqIqkEPoJFoiPnm/N3t5OQN40PrXWIJnkqb9gVaa3P Z1BQ== MIME-Version: 1.0 X-Received: by 10.68.169.161 with SMTP id af1mr20791765pbc.22.1375217102114; Tue, 30 Jul 2013 13:45:02 -0700 (PDT) Sender: nikolai.weibull@gmail.com In-Reply-To: <51F7E485.6050701@googlemail.com> References: <51F7E485.6050701@googlemail.com> Date: Tue, 30 Jul 2013 22:45:02 +0200 X-Google-Sender-Auth: 69JCjL1CsrmVRBeD8HruHkp27ug Message-ID: Subject: Re: [PATCH 12/16] _git: correct some "undocumented" options From: Nikolai Weibull To: m0viefreak Cc: =?UTF-8?Q?=C3=98ystein_Walle?= , zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2013 at 6:06 PM, m0viefreak wrote: > So what's the best way to go forward? > Should a [PATCH 17] be added and re-insert those > # TODO: > comments for options that are still missing in the git docs? I wouldn=E2=80=99t worry about it, but please, if you find the time, send t= he Git project the relevant patches to their documentation as well. I should have done it myself, but I never got around to it, and for that I=E2=80=99m apologetic.