From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2020, #10; Tue, 31)
Date: Thu, 2 Apr 2020 17:10:10 +0100 [thread overview]
Message-ID: <3b472af5-2b23-a155-78b5-cf28c3494864@gmail.com> (raw)
In-Reply-To: <xmqq4ku46s8z.fsf@gitster.c.googlers.com>
Hi Junio
On 01/04/2020 00:04, 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.
>
> [...]
>
> * dl/merge-autostash (2020-03-24) 19 commits
> - pull: pass --autostash to merge
> - t5520: make test_pull_autostash() accept expect_parent_num
> - merge: teach --autostash option
> - sequencer: implement save_autostash()
> - sequencer: unlink autostash in apply_autostash()
> - sequencer: extract perform_autostash() from rebase
> - rebase: generify create_autostash()
> - rebase: extract create_autostash()
> - reset: extract reset_head() from rebase
> - rebase: generify reset_head()
> - rebase: use apply_autostash() from sequencer.c
> - sequencer: make apply_rebase() accept a path
> - rebase: use read_oneliner()
> - sequencer: make read_oneliner() extern
> - sequencer: configurably warn on non-existent files
> - sequencer: make read_oneliner() accept flags
> - sequencer: use file strbuf for read_oneliner()
> - t7600: use test_write_lines()
> - Makefile: ASCII-sort += lists
>
> "git merge" learns the "--autostash" option.
>
> Will merge to 'next'.
I've posted some comments on this today, I'm not sure about the behavior
of 'git reset' after 'git merge --autostash'
Best Wishes
Phillip
next prev parent reply other threads:[~2020-04-02 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 23:04 What's cooking in git.git (Mar 2020, #10; Tue, 31) Junio C Hamano
2020-04-02 6:56 ` Miriam R.
2020-04-02 17:42 ` Junio C Hamano
2020-04-02 12:42 ` Garima Singh
2020-04-02 17:40 ` Junio C Hamano
2020-04-02 16:10 ` Phillip Wood [this message]
2020-04-03 20:04 ` Taylor Blau
2020-04-03 22:13 ` Junio C Hamano
2020-04-03 22:56 ` Emily Shaffer
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=3b472af5-2b23-a155-78b5-cf28c3494864@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
/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).