Hi Patrick! Thanks for the pleasant read! I thought this was a great topic for Review Club. It's too bad that we missed you, but we post all relevant feedback here anyway. Nevertheless, if you'd like to see the meeting notes, you can find them at: https://docs.google.com/document/d/14L8BAumGTpsXpjDY8VzZ4rRtpAjuGrFSRqn3stCuS_w/edit Patrick Steinhardt <ps@xxxxxx> writes: > Parsing the output of fetches is mostly impossible. It prettifies > reference names that are about to be updated, doesn't print the old and > new object IDs the refs are being updated from and to, and prints all of > that information in nice columns. In short, it is designed to be read by > humans rather than machines. > > This makes it hard to use in a script way though, e.g. to learn about > which references actually have been updated or which have not been > updated. This patch series intends to fix that by introducing a new > machine-parseable interface: > > ``` > $ git fetch --output-format=porcelain --no-progress > fff5a5e7f528b2ed2c335991399a766c2cf01103 af67688dca57999fd848f051eeea1d375ba546b2 refs/remotes/origin/master > * 0000000000000000000000000000000000000000 e046fe5a36a970bc14fbfbcb2074a48776f6b671 refs/remotes/origin/x86-rep-insns > * 0000000000000000000000000000000000000000 bb81ed6862b864c9eb99447f04d49a84ecb647e5 refs/tags/v6.3-rc4 > * 0000000000000000000000000000000000000000 83af7b1468c0dca86b4dc9e43e73bfa4f38d9637 refs/tags/v6.3-rc5 > * 0000000000000000000000000000000000000000 ab3affb8ed84f68638162fe7e6fd4055e15bff5b refs/tags/v6.3-rc6 > * 0000000000000000000000000000000000000000 1c8c28415e8743368a2b800520a6dd0b22ee6ec2 refs/tags/v6.3-rc7 > ``` Having machine-parseable output seems like an obviously good goal to me. The finer points of the interface and output format are worth discussing. I'll do so in the patches themselves. Overall, I found the series very well-structured and easy to follow along. Thanks.
