<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 15 Mar 2023, at 14:15, Dan Heidinga <<a href="mailto:heidinga@redhat.com" class="">heidinga@redhat.com</a>> wrote:</div>
<div class=""><br class="">
<div class="gmail_quote" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">
<div class=""><br class="">
</div>
<div class="">The high order bit in this approach is being able to use jlink to condense a runtime image, and then use jlink to condense it further. Do you have concerns with the high order bit? We can talk about size benefits (a secondary benefit) once we
all agree on the high order bit.</div>
<div class=""><br class="">
</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>I think we’ve seen two different high-order bits, but I can more readily understand your motivation, as you state it: it will allow an image to be an intermediate form in a condensing pipeline. It then depends on the question of whether or not that’s the
desired intermediate format, which is a clear question with a clear outcome.</div>
<div><br class="">
</div>
<div>— Ron</div>
<br class="">
</body>
</html>