From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git <git@vger.kernel.org>, Alex Henrie <alexhenrie24@gmail.com>
Subject: Re: What's cooking in git.git (Nov 2020, #06; Mon, 30)
Date: Tue, 1 Dec 2020 22:33:18 -0600 [thread overview]
Message-ID: <CAMP44s3c3UiSBUXGfmMi7tTLik6JQv+fDsii0HYOJAx3r2ZXWA@mail.gmail.com> (raw)
In-Reply-To: <xmqqtut6qf7q.fsf@gitster.c.googlers.com>
On Mon, Nov 30, 2020 at 11:19 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'seen' (formerly '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.
What happened to the git pull ff-only topic?
There's about three proposals flying around with no feedback [1][2][3].
In the meantime the annoying warning is still there.
[1] https://lore.kernel.org/git/20201125032938.786393-1-felipe.contreras@gmail.com/
[2] https://lore.kernel.org/git/20201125020931.248427-2-alexhenrie24@gmail.com/
[3] https://lore.kernel.org/git/20201123224621.2573159-2-felipe.contreras@gmail.com/
--
Felipe Contreras
next prev parent reply other threads:[~2020-12-02 4:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 5:15 What's cooking in git.git (Nov 2020, #06; Mon, 30) Junio C Hamano
2020-12-01 9:46 ` [PATCH] cook: add github.com/git-vcs/git as a URL Ævar Arnfjörð Bjarmason
2020-12-01 9:58 ` [PATCH] MaintNotes: use https:// instead of git:// when possible Ævar Arnfjörð Bjarmason
2020-12-01 11:54 ` Jeff King
2020-12-01 19:07 ` Junio C Hamano
2020-12-02 1:43 ` Jeff King
2020-12-01 11:47 ` [PATCH] cook: add github.com/git-vcs/git as a URL Jeff King
2020-12-01 19:10 ` Junio C Hamano
2020-12-02 1:44 ` Jeff King
2020-12-01 18:57 ` Junio C Hamano
2020-12-02 4:33 ` Felipe Contreras [this message]
2020-12-02 13:22 ` ds/config-literal-value (was Re: What's cooking in git.git (Nov 2020, #06; Mon, 30)) Derrick Stolee
2020-12-02 22:14 ` 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=CAMP44s3c3UiSBUXGfmMi7tTLik6JQv+fDsii0HYOJAx3r2ZXWA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).