git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / Atom feed
From: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
To: Junio C Hamano <gitster@pobox.com>
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: Thu, 15 Aug 2019 21:30:03 -0300
Message-ID: <CAHd-oW4qo=aTrA90RmWsLeW44WKUiL2x9rzdToFRMq=ebKYksQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqef1m4baf.fsf@gitster-ct.c.googlers.com>

On Thu, Aug 15, 2019 at 1:57 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Carlo Arenas <carenas@gmail.com> writes:
>
> > On Wed, Aug 14, 2019 at 4:58 PM Matheus Tavares Bernardino
> > <matheus.bernardino@usp.br> wrote:
> >>
> >> On Wed, Aug 14, 2019 at 6:27 PM Junio C Hamano <gitster@pobox.com> wrote:
> >> >
> >> [...]
> >> > * mt/grep-submodules-working-tree (2019-07-30) 1 commit
> >> >   (merged to 'next' on 2019-08-02 at e1a46a195f)
> >> >  + grep: fix worktree case in submodules
> >>
> >> There is a new version of this patch here[1], addressing the comments
> >> you and Christian made.
> >
> > since it is already in next, would be better to submit a patch on top
> > of the current topic instead (more details in
> > Documentation/SubmittingPatches).
>
> 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?

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 21:27 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 [this message]
2019-08-16 16:42         ` Junio C Hamano

Reply instructions:

You may reply publically 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAHd-oW4qo=aTrA90RmWsLeW44WKUiL2x9rzdToFRMq=ebKYksQ@mail.gmail.com' \
    --to=matheus.bernardino@usp.br \
    --cc=carenas@gmail.com \
    --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

git@vger.kernel.org list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox