zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] jp: fix segfaults during parameter expansion
Date: Sun, 21 Jan 2018 14:42:56 -0800	[thread overview]
Message-ID: <180121144256.ZM12835@torch.brasslantern.com> (raw)
In-Reply-To: <20180121202836.77alwuapsgbwzsbr@gmail.com>

On Jan 21, 10:28am, Joey Pabalinas wrote:
}
} When i send updated patches, what's the best format? A new email after
} a separate response mail, or as a single email with the response
} at the bottom (or some other third option, maybe)?

Typically replying below/inline with an edited excerpt of the message
is preferred (as I believe you have been doing) rather than top-posting.
Also generally one explains the patch first and puts the patch at the
bottom, rather than having the patch in the middle of the text, although
there can be common-sense exceptions if there's something about the
code that's easier to explain after it has been seen.

It's not necessary to go back to the start of the thread to respond
separately/directly to that.  Better if the patch comes at the end of
the discussion context that brought it about.


  reply	other threads:[~2018-01-21 22:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14  6:05 Joey Pabalinas
2018-01-14 12:06 ` Bart Schaefer
2018-01-14 12:07   ` Bart Schaefer
2018-01-14 14:05     ` [PATCH v2] " Joey Pabalinas
2018-01-14 14:01   ` [PATCH] " Joey Pabalinas
2018-01-14 14:10   ` dana
2018-01-20 16:16   ` Daniel Tameling
2018-01-20 23:38     ` Joey Pabalinas
2018-01-21  0:03     ` Bart Schaefer
2018-01-21  1:47       ` Joey Pabalinas
2018-01-21 17:43         ` Bart Schaefer
2018-01-21 20:28           ` Joey Pabalinas
2018-01-21 22:42             ` Bart Schaefer [this message]
2018-01-21 22:46               ` Joey Pabalinas
2018-01-21 20:29           ` Joey Pabalinas

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=180121144256.ZM12835@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).