mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Thorsten Scherer <t.scherer@eckelmann.de>
Subject: [ptxdist] [PATCH 0/3] git-ptx-patches: A fix and two minor improvements
Date: Wed, 29 Nov 2023 10:37:44 +0100	[thread overview]
Message-ID: <20231129093743.906378-1-u.kleine-koenig@pengutronix.de> (raw)

Hello,

occasionally I hit the problem that git-ptx-patches removes the From:
line from patches. I cannot reproduce that at will, but I think the
issue is fixed in the first patch. I hit that sometimes in the past with
no good idea how it could happen. Today Thorsten also hit it, which made
me look into the problem again and then I spotted the issue.

The other two patches are just minor improvements that I noticed while
researching for the race.

Best regards
Uwe

Uwe Kleine-König (3):
  git-ptx-patches: Fix a race condition
  git-ptx-patches: Open .ptxdist/series less often for writing
  git-ptx-patches: Simplify nested if construct

 scripts/git-ptx-patches | 24 +++++++++++++-----------
 1 file changed, 13 insertions(+), 11 deletions(-)

base-commit: 8d8f9a47d135920da7b70a5d71b763c457f4bcaf
-- 
2.42.0



             reply	other threads:[~2023-11-29  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  9:37 Uwe Kleine-König [this message]
2023-11-29  9:37 ` [ptxdist] [PATCH 1/3] git-ptx-patches: Fix a race condition Uwe Kleine-König
2023-11-30  6:09   ` Thorsten Scherer
2023-12-07 11:09   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-29  9:37 ` [ptxdist] [PATCH 2/3] git-ptx-patches: Open .ptxdist/series less often for writing Uwe Kleine-König
2023-12-07 11:09   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-29  9:37 ` [ptxdist] [PATCH 3/3] git-ptx-patches: Simplify nested if construct Uwe Kleine-König
2023-12-07 11:09   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20231129093743.906378-1-u.kleine-koenig@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=t.scherer@eckelmann.de \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox