From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Edward Thomson" <ethomson@edwardthomson.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
demerphq <demerphq@gmail.com>,
"Brandon Williams" <bmwill@google.com>,
"Derrick Stolee" <stolee@gmail.com>
Subject: Re: Questions about the hash function transition
Date: Fri, 24 Aug 2018 04:47:20 +0000 [thread overview]
Message-ID: <20180824044720.GG535143@genre.crustytoothpaste.net> (raw)
In-Reply-To: <20180824015438.GF99542@aiede.svl.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Thu, Aug 23, 2018 at 06:54:38PM -0700, Jonathan Nieder wrote:
> brian m. carlson wrote:
> > I realize I have a lot of code that has not been sent in yet, but I also
> > tend to build on my own series a lot, and I probably need to be a bit
> > better about extracting reusable pieces that can go in independently
> > without waiting for the previous series to land.
>
> For what it's worth, even if it all is in one commit with message
> "wip", I think I'd benefit from being able to see this code. I can
> promise not to critique it, and to only treat it as a rough
> premonition of the future.
It's in my object-id-partn branch at https://github.com/bk2204/git.
It doesn't do protocol v2 yet, but it does do protocol v1. It is, of
course, subject to change (especially naming) depending on what the list
thinks is most appropriate.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-08-24 4:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 14:02 Questions about the hash function transition Ævar Arnfjörð Bjarmason
2018-08-23 14:27 ` Junio C Hamano
2018-08-23 15:20 ` Ævar Arnfjörð Bjarmason
2018-08-23 16:13 ` Junio C Hamano
2018-08-24 1:40 ` brian m. carlson
2018-08-24 1:54 ` Jonathan Nieder
2018-08-24 4:47 ` brian m. carlson [this message]
2018-08-24 4:52 ` Jonathan Nieder
2018-08-24 1:47 ` Jonathan Nieder
2018-08-28 12:04 ` Johannes Schindelin
2018-08-28 12:49 ` Derrick Stolee
2018-08-28 17:12 ` Jonathan Nieder
2018-08-28 17:11 ` Jonathan Nieder
2018-08-29 13:09 ` Johannes Schindelin
2018-08-29 13:27 ` Derrick Stolee
2018-08-29 14:43 ` Derrick Stolee
2018-08-29 9:13 ` How is the ^{sha256} peel syntax supposed to work? Ævar Arnfjörð Bjarmason
2018-08-29 17:51 ` Stefan Beller
2018-08-29 17:59 ` Jonathan Nieder
2018-08-29 18:34 ` Stefan Beller
2018-08-29 18:41 ` Ævar Arnfjörð Bjarmason
2018-08-29 19:12 ` Jonathan Nieder
2018-08-29 19:37 ` Ævar Arnfjörð Bjarmason
2018-08-29 20:46 ` Jonathan Nieder
2018-08-29 23:45 ` Jeff King
2018-08-29 20:53 ` Junio C Hamano
2018-08-29 21:01 ` Jonathan Nieder
2018-08-29 17:56 ` Jonathan Nieder
2018-08-24 2:51 ` Questions about the hash function transition Jonathan Nieder
2018-08-28 13:50 ` Ævar Arnfjörð Bjarmason
2018-08-28 14:15 ` Edward Thomson
2018-08-28 15:02 ` Ævar Arnfjörð Bjarmason
2018-08-28 15:45 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824044720.GG535143@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=demerphq@gmail.com \
--cc=ethomson@edwardthomson.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=stolee@gmail.com \
--cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).