git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2022, #01; Mon, 2)
Date: Wed, 04 May 2022 17:03:33 -0700	[thread overview]
Message-ID: <xmqqa6bwluay.fsf@gitster.g> (raw)
In-Reply-To: <YnL2d4Vr9Vr7W4Hj@camp.crustytoothpaste.net> (brian m. carlson's message of "Wed, 4 May 2022 21:56:07 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> On 2022-05-02 at 22:27:46, Junio C Hamano wrote:
>> * bc/stash-export (2022-04-08) 4 commits
>>  - builtin/stash: provide a way to import stashes from a ref
>>  - builtin/stash: provide a way to export stashes to a ref
>>  - builtin/stash: factor out revision parsing into a function
>>  - object-name: make get_oid quietly return an error
>> 
>>  A mechanism to export and import stash entries to and from a normal
>>  commit to transfer it across repositories has been introduced.
>> 
>>  Will merge to 'next'?
>>  source: <20220407215352.3491567-1-sandals@crustytoothpaste.net>
>
> I think Ævar had some requests for a v5, so I'll try to get to one
> relatively soon.

Thanks.

      reply	other threads:[~2022-05-05  0:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 22:27 What's cooking in git.git (May 2022, #01; Mon, 2) Junio C Hamano
2022-05-03 21:19 ` Derrick Stolee
2022-05-04 16:18   ` Junio C Hamano
2022-05-05 15:04     ` Elijah Newren
2022-05-05 15:13       ` Derrick Stolee
2022-05-05 15:56       ` Junio C Hamano
2022-05-05 16:15         ` Elijah Newren
2022-05-05 18:53           ` Elijah Newren
2022-05-05 19:33             ` Junio C Hamano
2022-05-21 21:48             ` cone mode as default for sparse-checkout?, was " Johannes Schindelin
2022-05-04 21:56 ` brian m. carlson
2022-05-05  0:03   ` Junio C Hamano [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=xmqqa6bwluay.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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).