All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Coup <robert.coup@koordinates.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: What's cooking in git.git (Mar 2022, #03; Mon, 14)
Date: Tue, 15 Mar 2022 11:02:35 +0000	[thread overview]
Message-ID: <CAFLLRpLiCLiXkHNe2u4TKk-FjDy4LVZZR4qqxG+MamZYEFNUGg@mail.gmail.com> (raw)
In-Reply-To: <xmqq5yogp6xo.fsf@gitster.g>

Hi Junio,

On Mon, 14 Mar 2022 at 21:20, Junio C Hamano <gitster@pobox.com> wrote:
>
> * rc/fetch-refetch (2022-03-04) 7 commits
...
>  "git fetch --refetch" learned to fetch everything without telling
>  the other side what we already have, which is useful when you
>  cannot trust what you have in the local object store.
>
>  Waiting for discussion to settle.
>  cf. <20220309002729.3581315-1-calvinwan@google.com>
>  source: <pull.1138.v3.git.1646406274.gitgitgadget@gmail.com>

I am planning a re-roll for the boolean cli option, and I'll add some
more documentation as I proposed after Calvin's review.

It would be ace if Jonathan Tan can give it another once-over too,
though the key aspects of the implementation haven't changed since his
review of v1.

Thanks,
Rob :)

  parent reply	other threads:[~2022-03-15 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 21:20 What's cooking in git.git (Mar 2022, #03; Mon, 14) Junio C Hamano
2022-03-15  1:51 ` vd/stash-silence-reset (was: Re: What's cooking in git.git (Mar 2022, #03; Mon, 14)) Victoria Dye
2022-03-15 11:02 ` Robert Coup [this message]
2022-03-15 18:38 ` What's cooking in git.git (Mar 2022, #03; Mon, 14) Jeff Hostetler
2022-03-15 19:09   ` Junio C Hamano
2022-03-16 17:48 ` gc/recursive-fetch-with-unused-submodules (was Re: What's cooking in git.git (Mar 2022, #03; Mon, 14)) Glen Choo
2022-03-16 19:53   ` Junio C Hamano
2022-03-16 20:54     ` Glen Choo

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=CAFLLRpLiCLiXkHNe2u4TKk-FjDy4LVZZR4qqxG+MamZYEFNUGg@mail.gmail.com \
    --to=robert.coup@koordinates.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.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.