All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: tt/bisect-in-c, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)
Date: Tue, 29 Jan 2019 16:39:13 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1901291636270.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1901291506080.41@tvgsbejvaqbjf.bet>

Hi Junio,

On Tue, 29 Jan 2019, Johannes Schindelin wrote:

> On Mon, 28 Jan 2019, Junio C Hamano wrote:
> 
> > * tt/bisect-in-c (2019-01-02) 7 commits
> >  - bisect--helper: `bisect_start` shell function partially in C
> >  - bisect--helper: `get_terms` & `bisect_terms` shell function in C
> >  - bisect--helper: `bisect_next_check` shell function in C
> >  - bisect--helper: `check_and_set_terms` shell function in C
> >  - wrapper: move is_empty_file() and rename it as is_empty_or_missing_file()
> >  - bisect--helper: `bisect_write` shell function in C
> >  - bisect--helper: `bisect_reset` shell function in C
> > 
> >  More code in "git bisect" has been rewritten in C.
> > 
> >  Comments?
> 
> Just to make sure you know: both Chris and I reviewed the patches before
> Tanushree sent them off...

Oh, and I just realized that there are 4 merge conflicts with `master`,
all of them related to `the_repository` changes. So they should be easy
enough to resolve, even if I still think that it is a bad use of
maintainer's time, and asking contributors *not* to rebase projects too
much of distrust in contributors' skills in my mind.

So I suggested to Tanushree to ask you whether you prefer this not to be
rebased.

Ciao,
Dscho

  reply	other threads:[~2019-01-29 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 22:43 What's cooking in git.git (Jan 2019, #04; Mon, 28) Junio C Hamano
2019-01-29  7:22 ` Torsten Bögershausen
2019-01-29 12:54 ` pw/rebase-x-sanity-check, was " Johannes Schindelin
2019-01-29 18:11   ` Junio C Hamano
2019-01-29 14:03 ` js/rebase-am, " Johannes Schindelin
2019-01-29 14:06 ` tt/bisect-in-c, " Johannes Schindelin
2019-01-29 15:39   ` Johannes Schindelin [this message]
2019-01-29 14:15 ` en/rebase-merge-on-sequencer, " Johannes Schindelin
2019-01-29 14:21 ` Johannes Schindelin
2019-01-29 14:23 ` ps/stash-in-c, was " Johannes Schindelin
2019-01-29 14:26 ` [PATCH] Fix typos in whats-cooking.txt, " Johannes Schindelin

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=nycvar.QRO.7.76.6.1901291636270.41@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --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.