git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org, John Cai <johncai86@gmail.com>
Subject: Re: jc/stash-drop (was Re: What's cooking in git.git (Mar 2022, #02; Mon, 7))
Date: Wed, 09 Mar 2022 09:10:17 -0800	[thread overview]
Message-ID: <xmqqzglzm4qu.fsf@gitster.g> (raw)
In-Reply-To: <da1a464e-0beb-6a44-ed05-35868fd12bed@gmail.com> (Phillip Wood's message of "Wed, 9 Mar 2022 16:12:38 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

>> * jc/stash-drop (2022-03-02) 3 commits
>>   - stash: call reflog_delete() in reflog.c
>>   - reflog: libify delete reflog function and helpers
>>   - stash: add tests to ensure reflog --rewrite --updatref behavior
>>   "git stash drop" is reimplemented as an internal call to
>>   reflog_delete() function, instead of invoking "git reflog delete"
>>   via run_command() API.
>>   Will merge to 'next'.
>>   source: <pull.1218.v4.git.git.1646260044.gitgitgadget@gmail.com>
>
> I think John is planning to re-roll with an improved commit message
> c.f. <A8BDCB7C-5F16-4EDE-B8B7-0B73C93B68D2@gmail.com>

Thanks, but I think it already happened 24 hours ago.


  reply	other threads:[~2022-03-09 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  1:51 What's cooking in git.git (Mar 2022, #02; Mon, 7) Junio C Hamano
2022-03-08  8:05 ` Teng Long
2022-03-09 19:14   ` Junio C Hamano
2022-03-08 16:08 ` ds/partial-bundles (was Re: What's cooking in git.git (Mar 2022, #02; Mon, 7)) Derrick Stolee
2022-03-09 16:12 ` jc/stash-drop " Phillip Wood
2022-03-09 17:10   ` Junio C Hamano [this message]
2022-03-09 18:03 ` ar/submodule-udpate " Glen Choo
2022-03-09 19:27   ` Junio C Hamano
2022-03-09 22:09     ` Glen Choo

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=xmqqzglzm4qu.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johncai86@gmail.com \
    --cc=phillip.wood123@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).