zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Philippe Altherr <philippe.altherr@gmail.com>
Cc: "Daniel Shahaf" <d.s@daniel.shahaf.name>,
	zsh-workers@zsh.org, "Lawrence Velázquez" <larryv@zsh.org>
Subject: Re: Submitting multiple patches (was: Re: [PATCH] Fix ERR_EXIT behavior in function calls and "always" statements)
Date: Fri, 25 Nov 2022 18:28:34 -0800	[thread overview]
Message-ID: <CAH+w=7bP_9CEYZemnhfJht1CKCJEsc+RUPC-MaPOHjJWjVEzVg@mail.gmail.com> (raw)
In-Reply-To: <CAGdYchtgHez-xYsoq122gJF5ZZiXUXfgC-9AWzSUEfpnv4NZuA@mail.gmail.com>

On Wed, Nov 23, 2022 at 6:21 PM Philippe Altherr
<philippe.altherr@gmail.com> wrote:
>>
>> Namely, Philippe felt it important to
>> have one patch that completely backed out two or more of my previous
>> patches, followed by a patch that incorporated a useful part of one of
>> those patches.
>
> Did I do that?

Hmm.  When I copy-pasted the entire series of 4 patches from the
zsh-workers archive and put the whole thing through a single run of
"patch -p1", halfway through I got a "Reversed (or previously applied)
patch detected" message, which I told patch to ignore and it happily
finished.  But when I download them and apply them one at a time, that
doesn't happen.

So perhaps I misdiagnosed the reason for the "reversed".


  reply	other threads:[~2022-11-26  2:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 14:40 [PATCH] Fix ERR_EXIT behavior in function calls and "always" statements Philippe Altherr
2022-11-19 13:39 ` Philippe Altherr
2022-11-21  0:43   ` Bart Schaefer
2022-11-21  7:22     ` Lawrence Velázquez
2022-11-22  2:52       ` Philippe Altherr
2022-11-22  4:51         ` Bart Schaefer
2022-11-22 10:17         ` Peter Stephenson
2022-11-23  8:11           ` Lawrence Velázquez
2022-11-23  6:59         ` Lawrence Velázquez
2022-11-23  9:43           ` Philippe Altherr
2022-11-23 16:11             ` Bart Schaefer
2022-11-23 20:57               ` Submitting multiple patches (was: Re: [PATCH] Fix ERR_EXIT behavior in function calls and "always" statements) Daniel Shahaf
2022-11-23 21:11                 ` Bart Schaefer
2022-11-23 21:22                   ` Bart Schaefer
2022-11-23 21:54                   ` Bart Schaefer
2022-11-24  2:21                     ` Philippe Altherr
2022-11-26  2:28                       ` Bart Schaefer [this message]
2022-11-26  4:02                         ` Philippe Altherr
2022-11-24  1:47               ` [PATCH] Fix ERR_EXIT behavior in function calls and "always" statements Philippe Altherr
2022-11-24  4:28             ` Lawrence Velázquez

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='CAH+w=7bP_9CEYZemnhfJht1CKCJEsc+RUPC-MaPOHjJWjVEzVg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=larryv@zsh.org \
    --cc=philippe.altherr@gmail.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).