From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
"cohuck@redhat.com" <cohuck@redhat.com>
Subject: Re: [PATCH v3] editorial: replace hyperref with ref
Date: Mon, 15 Jul 2024 16:41:24 -0400 [thread overview]
Message-ID: <20240715163830-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481B7000236059EA3E243A7DCA02@PH0PR12MB5481.namprd12.prod.outlook.com>
On Sun, Jul 14, 2024 at 02:39:06PM +0000, Parav Pandit wrote:
>
>
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Sunday, July 14, 2024 8:07 PM
> > To: virtio-comment@lists.linux.dev; mst@redhat.com; cohuck@redhat.com
> > Cc: Parav Pandit <parav@nvidia.com>
> > Subject: [PATCH v3] editorial: replace hyperref with ref
> >
> > From: Parav Pandit <parav@nvidia.com>
> >
> > Replace hyperreference with the name reference.
> > Fix the broken reference link for the DEVICE_STATUS part.
> >
> > Fixes: aa4f6f069ab3 ("admin: Add admin commands for device parts")
> > Fixes: 617aa2d62a88 ("admin: Define common device parts")
> > Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > Message-ID: <20240713181540.3284147-1-parav@nvidia.com>
> >
> Missed to remove the message id in this error prone manual process. ☹
> Sending v4 now without the message id.
>
Shouldn't be manual.
The trick is that you should not send pull requests from
the same tree where you develop.
Instead, email patches, then use "b4 am" to get them
back from lore and apply them to another tree:
https://git.kernel.org/pub/scm/utils/b4/b4.git
test the result (detects instances of files you forgot to
add to git, etc), tag and send the pull request.
--
MST
prev parent reply other threads:[~2024-07-15 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 14:36 [PATCH v3] editorial: replace hyperref with ref Parav Pandit
2024-07-14 14:39 ` Parav Pandit
2024-07-15 20:41 ` Michael S. Tsirkin [this message]
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=20240715163830-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox