On Thu, Apr 27, 2023 at 04:20:12PM -0700, Glen Choo wrote: > Patrick Steinhardt <ps@xxxxxx> writes: > > On Wed, Apr 26, 2023 at 12:52:46PM -0700, Glen Choo wrote: > >> Patrick Steinhardt <ps@xxxxxx> writes: [snip] > > So with that in mind, I'd like to continue ignoring this issue for now > > and just not report the remote that the ref came from. But I'd also > > argue that we don't have to restrict porcelain mode to single-remote > > fetches: it can still be useful to do multi-remote fetches even without > > the information where a certain reference update comes from. So any kind > > of restriction would feel artificial to me here. > > > > Furthermore, I'd argue that it is not necessary to label the format as > > experimental only because of this limitation. With the refactorings done > > in this and the preceding patch series it is easy to add a new format in > > case there indeed is somebody that would have a usecase for this. The > > "porcelain" format should stay stable, and if we decide that we want to > > also report the remote for each reference in a follow-up we can easily > > add a "porcelain-v2" or "porcelain-with-remote" format. > > I agree that the current form is useful, but it seems quite likely that > users will want the remote name/url at some point. In the majority of > cases, the user can parse the remote name from the updated local ref and > if they want, they look up the url by asking "git config", but that > breaks down quite quickly if they have a custom refspec. > > My suggestion to label it experimental was meant to give us the freedom > to change the "first version" in backwards-incompatible ways that we > otherwise couldn't. We could say "here's porcelain-v2, use this and > ignore porcelain-v1", but it would be even nicer if the user didn't need > to think about porcelain-v1. The idea is that we could call it > experimental, see what users need in the wild, then make changes without > having to create a new "porcelain-v2" mode. > > (I realize in hindsight that calling it experimental sounds a bit > insulting. I thought your proposal was quite sensible, actually. i > apologize if it came across that way) No offense taken, so no need to apologize. > Perhaps part of the reason why you'd prefer not to make it experimental > is that users who might want this feature are too afraid of > backwards-incompatible changes. I think that's fair. Exactly. I'm implementing this whole feature with a concrete usecase at GitLab in mind, and if we declare this as experimental then it will become a whole lot more risky for us to actually adopt it. Because if the output format may change at any point in time, then the code that builds on top of it is likely to be broken. > A different way of > achieving the same flexibility would be to make the "porcelain" format > extensible (like git status --porcelain=v2). A future, multivalued > "--porcelain-options=show-remote-url,show-remote-ref" would cover > our bases. Yeah, that would indeed be quite flexible. Theoretically, there is no reason why we couldn't have `--output-format=porcelain,show-remote-url` though. > I'm happy with either approach as long as we don't have to bikeshed > about the "perfect" porcelain output :) Agreed, and that's why I'm currently defending the "good enough" format. It should likely work for most usecases that exist out there. The target audience is going to be quite small here as this is not a user-directed feature. Furthermore, I assume that the overlap of machines that want to parse all reference updates done in a multi-remote fetch while also being able to exactly tell which remote brought in what updates is going to be tiny. > >> > With these assumptions, the output format becomes unambiguously > >> > parseable. Furthermore, given that this output is designed to be > >> > consumed by scripts, the machine-readable data is printed to stdout > >> > instead of stderr like the human-readable output is. This is mostly done > >> > so that other data printed to stderr, like error messages or progress > >> > meters, don't interfere with the parseable data. > >> > >> Sending the 'main output' to stdout makes sense to me, but this (and > >> possibly respecting -z) sounds like a different mode of operation, not > >> just a matter of formats. It seems different enough that I'd prefer not > >> to piggyback on "fetch.output" for this (even though this adds more > >> surface to the interface...). > >> > >> We could add --porcelain and say that "fetch.output" is ignored if > >> --porcelain is also given. That also eliminates the need for > >> --output-format, I think. > > > > I was thinking about this initially, as well. But ultimately I decided > > against this especially because of your second paragraph: we'd now need > > to think about precedence of options and mutual exclusion, and that to > > me feels like an interface that is less obvious than a single knob that > > works as you'd expect. > > My full thoughts on this are in > > https://lore.kernel.org/git/kl6lildhlz3i.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > but the short version is that I'm not sure if I expect something as > innocuous-looking as --output-format would imply other, machine-friendly > things (like stdout instead of stderr), and using --porcelain might make > option precedence clearer in some situtations (like if -z is given). I'm not even sure that `-z` makes sense in this context. If we see cases where not using `-z` can cause the machine-readable interface to become unparseable then this is a bug in the output format, if you ask me. Mostly because the whole intent of it is to be machine-parseable. So if we output data that can e.g. contain newlines, then we must not use newlines as part of the output format or alternatively escape them. Why let the author of the script shoot themselves into the foot? Anyway, I'm digressing. It's hard for me to decide what to do right now. The thread with Junio and Jacob points into the direction of keeping the `--output-format=` interface, while this thread points into the other direction. I'm naturally more inclined to keep `--output-format=`, mostly because I personally feel like it's the more obvious interface. But I also see your point, so it's not really a choice of right-or-wrong here, but rather of style. Patrick
Attachment:
signature.asc
Description: PGP signature
