zsh-workers
 help / color / mirror / code / Atom feed
From: "Johan Sundström" <oyasumi@gmail.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: Nikolai Weibull <now@bitwi.se>, Zsh Workers <zsh-workers@zsh.org>
Subject: Re: Updated _git completion (not attached)
Date: Sat, 19 Mar 2011 19:24:20 -0700	[thread overview]
Message-ID: <AANLkTikORnKwpv7sysJk4Mo4uzEXhf4a939D9jBhJ1JH@mail.gmail.com> (raw)
In-Reply-To: <8739mki0uj.fsf@ft.bewatermyfriend.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Fri, Mar 18, 2011 at 14:18, Frank Terbeck <ft@bewatermyfriend.org> wrote:

> Nikolai Weibull wrote:
> [...]
> > OK, I’ve fixed the bugs and suggestions made in this thread.  How do
> > you (that is, the Zsh maintainers) want them submitted?  As a patch
> > series to this list?
>
> This document details how patches should be submitted:
>
> <
> http://zsh.git.sourceforge.net/git/gitweb.cgi?p=zsh/zsh;a=blob_plain;f=Etc/zsh-development-guide;hb=HEAD
> >
>

This document doesn't mention it yet, but I assume it's best to submit
patches in the message body rather than as attachments? (Unless, I suppose,
they contain binary content.)

That being said, the output of "git format-patch" is usable,
> too. Exchanging git's default "[PATCH]" by "PATCH: " would be extra
> sugar.
>

Running perl -pi -e 's/^(Subject: ).(PATCH[^]]*)./$1$2:/' *.patch on
format-patch files fixes that (it seems command line options to git can't).
Maybe a useful note for the dev guide?

-- 
 / Johan Sundström, http://ecmanaut.blogspot.com/

  reply	other threads:[~2011-03-20  2:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 20:34 Nikolai Weibull
2011-02-19 13:39 ` Simon Ruderich
2011-02-21 14:34   ` Simon Ruderich
2011-02-27  3:45 ` Wayne Davison
2011-02-27  7:47   ` Frank Terbeck
2011-02-27 12:03     ` Nikolai Weibull
2011-02-27 12:25       ` Nikolai Weibull
2011-02-28 13:58         ` Simon Ruderich
2011-02-28 16:33           ` Wayne Davison
2011-02-28 17:07             ` Nikolai Weibull
2011-02-28 17:21               ` Mikael Magnusson
2011-02-28 20:32               ` Simon Ruderich
2011-02-28 20:58         ` Frank Terbeck
2011-03-04 12:57         ` Frank Terbeck
2011-03-18 20:34           ` Nikolai Weibull
2011-03-18 20:43             ` Frank Terbeck
2011-03-18 21:09               ` Nikolai Weibull
2011-03-18 21:18                 ` Frank Terbeck
2011-03-20  2:24                   ` Johan Sundström [this message]
2011-03-20  8:05                     ` Submitting patches [was: Re: Updated _git completion (not attached)] Frank Terbeck
2011-03-20  8:47                       ` Bart Schaefer
2011-03-20 15:41                         ` Benjamin R. Haskell
2011-03-20 17:50                           ` Bart Schaefer
2011-03-20 15:34                       ` Benjamin R. Haskell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikORnKwpv7sysJk4Mo4uzEXhf4a939D9jBhJ1JH@mail.gmail.com \
    --to=oyasumi@gmail.com \
    --cc=ft@bewatermyfriend.org \
    --cc=now@bitwi.se \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).