Re: What's cooking in git.git (Jul 2019, #06; Thu, 25)

From: Rohit Ashiwal <rohit.ashiwal265@gmail.com>
Date: Jul 27, 2019, 19:38 UTC
Message-ID: <20190727193814.7400-1-rohit.ashiwal265@gmail.com>
In-Reply-To: <xmqq36itprzo.fsf@gitster-ct.c.googlers.com>

Hi Junio

On Thu, 25 Jul 2019 17:19:23 -0700 Junio C Hamano <gitster@pobox.com> wrote:

Show 15 quoted lines

> 
> [...]
> [New Topics]
> 
> * bb/grep-pcre2-bug-message-fix (2019-07-23) 1 commit
>   (merged to 'next' on 2019-07-23 at 8bd5a68618)
>  + grep: print the pcre2_jit_on value
> 
>  BUG() message fix.
> 
>  The codepath may want to just simply be removed, though.
> 
> 
> * ra/rebase-i-more-options (2019-07-23) 4 commits
>  - SQUASH???

There are only 3 commits in this "series".

>  - rebase -i: support --committer-date-is-author-date
>  - sequencer: add NULL checks under read_author_script
>  - rebase -i: add --ignore-whitespace flag

The correct order should be:
   - rebase -i: add --ignore-whitespace flag
   - sequencer: add NULL checks under read_author_script
   - rebase -i: support --committer-date-is-author-date

I'll soon send another revision and while on it, let's merge these topics into one. Should I also rebase them on the tip of git/git's master?

> [...]

Best Rohit