All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: ps/fetch-output-format (was: What's cooking in git.git (May 2023, #02; Fri, 5))
Date: Mon, 8 May 2023 09:31:33 +0200	[thread overview]
Message-ID: <ZFilVVv88qhZhL-d@ncase> (raw)
In-Reply-To: <xmqqmt2ibcq2.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

On Fri, May 05, 2023 at 04:05:57PM -0700, Junio C Hamano wrote:
> * ps/fetch-output-format (2023-05-03) 8 commits
>  - fetch: introduce machine-parseable "porcelain" output format
>  - fetch: move option related variables into main function
>  - fetch: move display format parsing into main function
>  - fetch: introduce `display_format` enum
>  - fetch: fix missing from-reference when fetching HEAD:foo
>  - fetch: add a test to exercise invalid output formats
>  - fetch: split out tests for output format
>  - fetch: fix `--no-recurse-submodules` with multi-remote fetches
> 
>  "git fetch" learned the "--output-format" option that emits what it
>  did in a machine-parseable format.
> 
>  Will merge to 'next'?
>  source: <cover.1683113177.git.ps@pks.im>

Note that the description isn't accurate anymore: v3 of the patch series
has changed the new option from `--output-format` to `--porcelain`. With
that change I'd also feel more comfortable if the new iteration had at
least one review before merging to `next`.

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-05-08  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 23:05 What's cooking in git.git (May 2023, #02; Fri, 5) Junio C Hamano
2023-05-08  7:31 ` Patrick Steinhardt [this message]
2023-05-08 16:38 ` Felipe Contreras
2023-05-08 20:59 ` Derrick Stolee
2023-05-08 21:40   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZFilVVv88qhZhL-d@ncase \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.