From: Kristoffer Haugsbakk Date: Wed, 04 Jun 2025 14:09:33 GMT Subject: Re: [PATCH 1/2] contrib/subtree: parse using --stuck-long Message-ID: <0c65723e-fb52-43e1-8bf2-32bd421163a1@app.fastmail.com> In-Reply-To: On Wed, Jun 4, 2025, at 15:56, Patrik Weiskircher wrote: >> >> Here we mention "-S", but that flag isn't implemented yet, right? >> >> Perhaps something like: >> >> Optional parameter handling only works unambiguous with git rev-parse >> --parseopt when using the --stuck-long option. To prepare for future commits >> which add flags with optional parameters, parse with --stuck-long. >> > > Makes sense! Changing that. What is a good policy to resubmit > something? Should I wait longer? Sorry, very new here! • Force-push your branch to gitgitgadget • Edit the PR description with something like “Changes since v1:” to summarize the changes • (`/preview` comment) • To send the next version: `/submit` comment again I think that’s it. :) I don’t think there’s a need to wait if you don’t want to. -- Kristoffer Haugsbakk