From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2023, #01; Tue, 2)
Date: Wed, 03 May 2023 10:36:42 -0700 [thread overview]
Message-ID: <xmqqa5yltiz9.fsf@gitster.g> (raw)
In-Reply-To: 6451d97570a4a_2ac9f29445@chronos.notmuch
Felipe Contreras <felipe.contreras@gmail.com> writes:
> What's wrong with:
> https://lore.kernel.org/git/20230418011828.47851-1-felipe.contreras@gmail.com/
By itself there may not be. And we have the "checkout" thing that
may have been made worse updated already on the 'master' front, so
this should be a good addition.
Thanks for pinging. Queued on top of the more recent 'master'.
next prev parent reply other threads:[~2023-05-03 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 22:49 What's cooking in git.git (May 2023, #01; Tue, 2) Junio C Hamano
2023-05-03 3:48 ` Felipe Contreras
2023-05-03 17:36 ` Junio C Hamano [this message]
2023-05-03 20:38 ` johncai86
2023-05-03 21:21 ` Junio C Hamano
2023-05-04 10:55 ` M Hickford
2023-05-04 15:13 ` Junio C Hamano
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=xmqqa5yltiz9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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).