All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"mvaralar@redhat.com" <mvaralar@redhat.com>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [PATCH 0/4] editorial: Prepare master branch for 1.4 spec release
Date: Mon, 27 Oct 2025 14:06:46 -0400	[thread overview]
Message-ID: <20251027140542-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CY8PR12MB7195D654CC8553C5B686105ADCFCA@CY8PR12MB7195.namprd12.prod.outlook.com>

On Mon, Oct 27, 2025 at 06:04:22PM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: 27 October 2025 11:27 PM
> > 
> > On Mon, Oct 27, 2025 at 07:47:52PM +0200, Parav Pandit wrote:
> > > Hi All,
> > >
> > > This short series prepares the specification for release 1.4 version
> > > from the master branch.
> > 
> > 
> > I noticed you updated latexdiff module - intentional?
> >
> I didn't. :( 
> Latexdiff is able to generate the necessary diff without my changelog patches.
> Below is the version I am using for last sometime.
> 
> latexdiff --version
> This is LATEXDIFF 1.3.1a  (Algorithm::Diff 1.15 fast, Perl v5.34.0)
>   (c) 2004-2018 F J Tilmann
> 

changelog is not supposed to affect diff at all.

Also I think we need to have changelog 1.2 to 1.3 preserved
for now (separately).
I do not see it there.

> > > note:
> > > makediffpdf.sh still have fails and needs resolution. WIP.
> > >
> > > Parav Pandit (4):
> > >   edit: remove old changelog
> > >   edit: add changelog for 1.4
> > >   edit: Remove annotation of special character
> > >   REVISION: update to 1.4
> > >
> > >  REVISION      |    2 +-
> > >  REVISION-DATE |    2 +-
> > >  cl-cs05.tex   | 2120 ++++++++++++++++++++++++++++++++++++++++
> > >  cl-os.tex     | 2605 ++++++++++++++++++++++++-------------------------
> > >  4 files changed, 3407 insertions(+), 1322 deletions(-)  create mode
> > > 100644 cl-cs05.tex
> > >
> > > --
> > > 2.34.1


  reply	other threads:[~2025-10-27 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 17:47 [PATCH 0/4] editorial: Prepare master branch for 1.4 spec release Parav Pandit
2025-10-27 17:47 ` [PATCH 1/4] edit: remove old changelog Parav Pandit
2025-10-27 17:47 ` [PATCH 2/4] edit: add changelog for 1.4 Parav Pandit
2025-10-27 17:47 ` [PATCH 3/4] edit: Remove annotation of special character Parav Pandit
2025-10-27 17:47 ` [PATCH 4/4] REVISION: update to 1.4 Parav Pandit
2025-10-27 17:56 ` [PATCH 0/4] editorial: Prepare master branch for 1.4 spec release Michael S. Tsirkin
2025-10-27 18:04   ` Parav Pandit
2025-10-27 18:06     ` Michael S. Tsirkin [this message]
2025-10-30 10:57       ` Parav Pandit
2025-10-27 18:08     ` Michael S. Tsirkin
2025-10-30 10:54       ` Parav Pandit
2025-10-30 10:59         ` Michael S. Tsirkin
2025-10-30 15:15           ` Parav Pandit
2025-11-06 15:42             ` Michael S. Tsirkin
2025-11-06 15:50             ` Michael S. Tsirkin
2025-10-27 18:05 ` Michael S. Tsirkin

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=20251027140542-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=mvaralar@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@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 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.