git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Rohit Ashiwal <rohit.ashiwal265@gmail.com>
Subject: Re: What's cooking in git.git (Oct 2019, #05; Fri, 18)
Date: Thu, 24 Oct 2019 11:04:41 +0100	[thread overview]
Message-ID: <99072e19-c732-15d1-f4a3-50cc02c9e21a@gmail.com> (raw)
In-Reply-To: <xmqqblue5zxc.fsf@gitster-ct.c.googlers.com>

On 18/10/2019 07:29, Junio C Hamano wrote:
> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
> 
> * ra/rebase-i-more-options (2019-09-09) 6 commits
>  - rebase: add --reset-author-date
>  - rebase -i: support --ignore-date
>  - sequencer: rename amend_author to author_to_rename
>  - rebase -i: support --committer-date-is-author-date
>  - sequencer: allow callers of read_author_script() to ignore fields
>  - rebase -i: add --ignore-whitespace flag
> 
>  "git rebase -i" learned a few options that are known by "git
>  rebase" proper.
> 
>  Needs to consider existing GIT_COMMITTER_DATE environment, etc.
>  cf. <5adde732-173b-d24d-d23f-bb4d043076d7@gmail.com>

The test coverage is also lacking cf.
<ed8e65a2-72e8-210c-d4a4-eacdb5c7b0e8@gmail.com>

Best Wishes

Phillip

      reply	other threads:[~2019-10-24 10:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  6:29 What's cooking in git.git (Oct 2019, #05; Fri, 18) Junio C Hamano
2019-10-24 10:04 ` Phillip Wood [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=99072e19-c732-15d1-f4a3-50cc02c9e21a@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rohit.ashiwal265@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).