All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Kloudifold <cloudifold.3125@gmail.com>
Cc: alison.schofield@intel.com, outreachy@lists.linux.dev
Subject: Re: Help in patch message
Date: Tue, 14 Mar 2023 07:13:32 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2303140711370.2705@hadrien> (raw)
In-Reply-To: <ZA/Tql5l6dfNaMZ7@CloudiRingWorld>

> Recently, I submitted a patch that has been rejected, and I am not
> sure whether to go ahead and fix it or create a new one.
> I would greatly appreciate your guidance on how to proceed

Please include relevant context in your message.  If a patch has been
rejected, eg someone says "This change is not a good idea for reason XYZ",
then you should move on to something else.  If you have gotten some
feedback on a patch, you should follow the feedback, and try to improve
the patch.

julia

  parent reply	other threads:[~2023-03-14  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  1:53 Help in patch message Kloudifold
2023-03-14  4:40 ` Bagas Sanjaya
2023-03-14  6:13 ` Julia Lawall [this message]
2023-03-14  6:30 ` Khadija Kamran
2023-03-14 16:15 ` Alison Schofield

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=alpine.DEB.2.22.394.2303140711370.2705@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=alison.schofield@intel.com \
    --cc=cloudifold.3125@gmail.com \
    --cc=outreachy@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.