Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: Carlo Arenas <carenas@gmail.com>, git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2019, #04; Wed, 14)
Date: Fri, 16 Aug 2019 09:42:31 -0700	[thread overview]
Message-ID: <xmqqlfvt12q0.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAHd-oW4qo=aTrA90RmWsLeW44WKUiL2x9rzdToFRMq=ebKYksQ@mail.gmail.com> (Matheus Tavares Bernardino's message of "Thu, 15 Aug 2019 21:30:03 -0300")

Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:

>> Thanks.  Or we could just go the lazier route.  A new stable release
>> would happen within a day or two, and then in a week or so after that,
>> the tip of 'next' gets rewound and rebuilt on top of it.  We can
>> discard the older copy and replace with the newer one when it happens.
>
> OK. I'm working on a v2 of mt/threaded-grep-in-object-store which
> might depend on this patch. I can then send the newer version of this
> patch as part of the series. Is that OK?

That would be good---just tell me what stale one I (may) still have
in my tree that I need to discard when it happens.  Thanks.

      reply	other threads:[~2019-08-16 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 21:27 What's cooking in git.git (Aug 2019, #04; Wed, 14) Junio C Hamano
2019-08-14 23:18 ` Matheus Tavares Bernardino
2019-08-15  2:15   ` Carlo Arenas
2019-08-15 16:56     ` Junio C Hamano
2019-08-16  0:30       ` Matheus Tavares Bernardino
2019-08-16 16:42         ` Junio C Hamano [this message]

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=xmqqlfvt12q0.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox