<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Nov 4, 2020, at 3:01 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Nicolas.<div><br></div><div>> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">If possible it should be scripted because it's really time consuming to clean up via web interface.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Most of the cases, I suppose, are that copy-vs-move mistake. We do need a "move" button in the MC GUI. </span></div></div></div></blockquote><div><br></div>Agreed.<div><br></div><div>But I don’t think we should move *any* package from inbox to trunk unless it has already been moved. The right place for inbox submissions that have been reviewed is the treated inbox. Why?</div><div><br></div><div>A submission to inbox that passes review as is can simply be moved to inbox. That is the natural thing a reviewer will do. But occasionally, as has happened with Kernel over the past few days, an inbox submission will need merging. It is the merge that ends up in trunk. The original inbox submission may be invalid; at worse it could cause the system to lock up or crash if loaded, say as part of an update test starting from the last release and loading all packages in trunk.</div><div><br></div><div>So I don’t understand why we’re moving things en masse to trunk rather than treated inbox.</div><div><br><blockquote type="cite"><div dir="ltr"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000"><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 04.11.2020 11:53:15 schrieb Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr"><div>Hi Marcel,</div><div>months ago, I'm pretty sure that I did similar clean up, but I had the impression that some files did come back...</div><div>Such clean-up is very important because any extra file in inbox costs reviewers time which is a very scarce resource.</div><div>If possible it should be scripted because it's really time consuming to clean up via web interface.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 4 nov. 2020 à 11:44, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de">marcel.taeumel@hpi.de</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="gmail-m_-8900247086229378905__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)">Hi all!<div></div><div><br></div><div>I just moved over all Kernel Inbox versions that where already in Trunk. Please move, not copy. Thanks! :-)</div><div><br></div><div>Best,</div><div>Marcel</div></div><br>
</blockquote></div>
</div></blockquote>
</div><span></span><br></div></blockquote></div></body></html>