From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: George Dunlap <George.Dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>, Ian Jackson <iwj@xenproject.org>,
Committers <committers@xenproject.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] RFC: Version support policy
Date: Tue, 22 Feb 2022 13:34:42 +0100 [thread overview]
Message-ID: <YhTYYven0PMcHM4P@mail-itl> (raw)
In-Reply-To: <YhTUe7K5/rlek4AA@invisiblethingslab.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Tue, Feb 22, 2022 at 01:18:03PM +0100, Wojtek Porczyk wrote:
> On Mon, Feb 14, 2022 at 09:50:25PM +0000, George Dunlap wrote:
> > I think it’s too much effort to ask developers to try to find the actual
> > minimum version of each individual dependency as things evolve.
>
> By "find the actual minimum version", do you mean to get to know the version
> number, or install that version on developer's machine?
I think it's something else (closer to the second one): finding what
version is required for features actually used in the code.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-22 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:37 [PATCH] RFC: Version support policy Ian Jackson
2021-08-18 11:16 ` Marek Marczykowski-Górecki
2022-02-14 21:31 ` George Dunlap
2021-08-19 9:18 ` Jan Beulich
2021-08-19 11:55 ` Ian Jackson
2021-08-19 12:00 ` Jan Beulich
2022-02-14 21:50 ` George Dunlap
2022-02-15 8:20 ` Jan Beulich
2022-02-28 14:46 ` George Dunlap
2022-02-22 12:18 ` Wojtek Porczyk
2022-02-22 12:34 ` Marek Marczykowski-Górecki [this message]
2022-02-22 14:58 ` George Dunlap
2022-02-22 15:05 ` Jan Beulich
2022-02-22 15:42 ` Marek Marczykowski-Górecki
2022-02-23 13:20 ` George Dunlap
2022-02-23 14:52 ` Wojtek Porczyk
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=YhTYYven0PMcHM4P@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=committers@xenproject.org \
--cc=iwj@xenproject.org \
--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.