All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <iwj@xenproject.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	"xen-devel\@lists.xenproject.org"
	<xen-devel@lists.xenproject.org>,
	Ian Jackson <ian.jackson@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Anthony Perard <anthony.perard@citrix.com>,
	Julien Grall <julien@xen.org>
Subject: Re: preparations for 4.15.1 and 4.13.4 [and 1 more messages]
Date: Thu, 19 Aug 2021 18:04:46 +0100	[thread overview]
Message-ID: <24862.36654.996255.14674@mariner.uk.xensource.com> (raw)
In-Reply-To: <24862.36076.875216.461840@mariner.uk.xensource.com>

Ian Jackson writes ("Re: preparations for 4.15.1 and 4.13.4 [and 1 more messages]"):
> I thought of a better way to do this.  See below for proposed patch to
> xen.git#staging.

We discussed this on IRC, and I'm going to drop this patch.

Ian.

18:00 <@andyhhp> I'm debating what to say there
18:01 <@Diziet> I thought of this since otherwise we're just setting ourselves 
                up to make a mistake.
18:01 <@andyhhp> I'm tempted to just leave it all alone.  That comment will go 
                 stale very quickly, and the general rule is applicable to 
                 other libs
18:01 <@Diziet> True
18:01 <@andyhhp> evidence suggests that almost all edits to the soname require 
                 a fixup...
18:01 <@Diziet> haha
18:01 <@Diziet> FE
18:01 <@andyhhp> it would be nice to do something better
18:02 <@andyhhp> and the "bump the soname proactively" is almost very nice for 
                 that.  My first thought was to suggest that we change to that 
                 as a default way of working
18:01 <@Diziet> haha
18:01 <@Diziet> FE
18:01 <@andyhhp> it would be nice to do something better
18:02 <@andyhhp> and the "bump the soname proactively" is almost very nice for 
                 that.  My first thought was to suggest that we change to that 
                 as a default way of working
18:02 <@andyhhp> but it gets you into a position where you're off-by-one when 
                 it comes to the release
18:02 <@Diziet> Mmmm
18:03 <@Diziet> OK, well, I'll drop my patch for now then if you don't feel 
                it's worth it.
18:03 <@Diziet> Thanks for the reviews, anyway.


  reply	other threads:[~2021-08-19 17:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15  7:58 preparations for 4.15.1 and 4.13.4 Jan Beulich
2021-07-02 14:29 ` [PATCH-4.15] tools/libs/ctrl: fix xc_core_arch_map_p2m() to support linear p2m table Juergen Gross
2021-07-16  6:47   ` Juergen Gross
2021-08-19  7:45     ` Juergen Gross
2021-08-19 16:11       ` Ian Jackson
2021-08-19 15:44     ` preparations for 4.15.1 and 4.13.4 support linear p2m table [and 1 more messages] Ian Jackson
2021-07-15  8:02 ` preparations for 4.15.1 and 4.13.4 Jan Beulich
2021-07-15  9:02 ` Anthony PERARD
2021-08-19 16:23   ` QEMU 6.0+ in 4.15 and 4.14 (Re: preparations for 4.15.1 and 4.13.4) Ian Jackson
2021-08-23  9:48     ` Olaf Hering
2021-08-27 12:39     ` Anthony PERARD
2021-07-15 10:58 ` preparations for 4.15.1 and 4.13.4 Andrew Cooper
2021-07-15 11:12   ` Jan Beulich
2021-07-15 14:11 ` Olaf Hering
2021-07-15 14:21   ` Jan Beulich
2021-08-19 16:46   ` Ian Jackson
2021-08-23  8:42     ` Olaf Hering
2021-07-15 17:16 ` Andrew Cooper
2021-07-16  6:16   ` Jan Beulich
2021-08-19 16:43   ` preparations for 4.15.1 and 4.13.4 [and 1 more messages] Ian Jackson
2021-08-19 16:55     ` Ian Jackson
2021-08-19 17:04       ` Ian Jackson [this message]
2021-08-19 16:56     ` Andrew Cooper
2021-08-20  6:10     ` Jan Beulich
2021-07-16  7:41 ` preparations for 4.15.1 and 4.13.4 Julien Grall
2021-07-16 20:16   ` Stefano Stabellini
2021-07-19 10:32 ` Jan Beulich
2021-08-19 16:49   ` Ian Jackson

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=24862.36654.996255.14674@mariner.uk.xensource.com \
    --to=iwj@xenproject.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.
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.