From: brian m. carlson Date: Sun, 29 Oct 2023 14:18:57 GMT Subject: Re: [PATCH 1/1] merge-file: add an option to process object IDs Message-ID: In-Reply-To: On 2023-10-29 at 06:17:09, Elijah Newren wrote: > Hi, > > Overall, looks good. Just a couple questions... > > On Tue, Oct 24, 2023 at 12:58 PM brian m. carlson > wrote: > > > > From: "brian m. carlson" > > > [...] > > --- a/Documentation/git-merge-file.txt > > +++ b/Documentation/git-merge-file.txt > > @@ -12,6 +12,9 @@ SYNOPSIS > > 'git merge-file' [-L [-L [-L ]]] > > [--ours|--theirs|--union] [-p|--stdout] [-q|--quiet] [--marker-size=] > > [--[no-]diff3] > > +'git merge-file' --object-id [-L [-L [-L ]]] > > + [--ours|--theirs|--union] [-q|--quiet] [--marker-size=] > > + [--[no-]diff3] > > Why was the `[-p|--stdout]` option removed in the second synopsis? > Elsewhere you explicitly call it out as a possibility to be used with > --object-id. Originally because it implied `-p`, but I changed that to write into the object store. I'll restore it. > Also, why the extra synopsis instead of just adding a `[--object-id]` > option to the previous one? Because there's a relevant difference: the former has , , and , and the latter has the -oid versions. > Does "/dev/null" have any portability considerations? (I really don't > know; just curious.) We already use it elsewhere in the codebase, so I assume it works. We also have a test for that case and it worked in CI, so it's probably fine. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA