From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2022, #07; Mon, 24)
Date: Fri, 28 Jan 2022 22:31:44 +0000 [thread overview]
Message-ID: <YfRu0G9aNQxT3vtl@camp.crustytoothpaste.net> (raw)
In-Reply-To: <xmqq35lc53e9.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On 2022-01-24 at 19:39:58, Junio C Hamano wrote:
> * bc/clarify-eol-attr (2022-01-12) 2 commits
> - docs: correct documentation about eol attribute
> - t0027: add tests for eol without text in .gitattributes
>
> Doc and test update around the eol attribute.
> source: <20220111021507.531736-1-sandals@crustytoothpaste.net>
I'll try to take a look at the feedback here and possibly send another
round.
> * bc/csprng-mktemps (2022-01-17) 2 commits
> - wrapper: use a CSPRNG to generate random file names
> - wrapper: add a helper to generate numbers from a CSPRNG
>
> Pick a better random number generator and use it when we prepare
> temporary filenames.
>
> Are we solving the right problem?
> cf. <220118.86zgntpegy.gmgdl@evledraar.gmail.com>
> source: <20220117215617.843190-1-sandals@crustytoothpaste.net>
It sounds like folks would prefer we drop this series. I'm not planning
to send an alternate approach here.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2022-01-28 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 19:39 What's cooking in git.git (Jan 2022, #07; Mon, 24) Junio C Hamano
2022-01-25 19:45 ` Submodule UX overhaul update (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Emily Shaffer
2022-01-26 14:09 ` Ævar Arnfjörð Bjarmason
2022-01-26 17:27 ` Emily Shaffer
2022-01-26 15:16 ` Kaartic Sivaraam
2022-01-26 16:35 ` Atharva Raykar
2022-01-26 17:43 ` Emily Shaffer
2022-01-26 17:50 ` Glen Choo
2022-01-28 7:40 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs (Was: " Patrick Steinhardt
2022-01-28 21:14 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs Junio C Hamano
2022-01-31 9:50 ` flags types/names (was: ps/avoid-unnecessary-hook-invocation-with-packed-refs) Han-Wen Nienhuys
2022-01-31 17:13 ` flags types/names Junio C Hamano
2022-01-28 22:31 ` brian m. carlson [this message]
2022-02-04 0:27 ` What's cooking in git.git (Jan 2022, #07; Mon, 24) Junio C Hamano
2022-02-04 17:27 ` René Scharfe
2022-02-02 11:28 ` ab/auto-detect-zlib-compress2 (was: What's cooking in git.git (Jan 2022, #07; Mon, 24)) Ævar Arnfjörð Bjarmason
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=YfRu0G9aNQxT3vtl@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--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).