From: list at eworm.de (Christian Hesse)
Subject: RFC: replace 'unsigned char sha1[20]' with 'struct object_id oid'
Date: Thu, 29 Sep 2016 22:27:22 +0200 [thread overview]
Message-ID: <20160929222722.64de8fa3@leda.localdomain> (raw)
Hello everybody,
upstream git is replacing 'unsigned char sha1[20]' with 'struct object_id
oid'. We have some code that can be changed independent from upstream. So
here we go...
The following changes since commit 11695a58fd732689be486edf88d145578a787c89:
git: update to v2.10.0 (2016-09-04 12:38:18 +0200)
are available in the git repository at:
ssh://git at git.zx2c4.com/cgit ch/sha1-oid
for you to fetch changes up to 0a8ac85a21bd9db1b002dd5658c48f36dc3902af:
ui-tree: replace 'unsigned char sha1[20]' with 'struct object_id
oid' (2016-09-29 22:17:07 +0200)
----------------------------------------------------------------
Christian Hesse (10):
cgit: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-blob: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-commit: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-log: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-patch: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-plain: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-shared: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-snapshot: replace 'unsigned char sha1[20]' with 'struct object_id
oid'
ui-tag: replace 'unsigned char sha1[20]' with 'struct object_id oid'
ui-tree: replace 'unsigned char sha1[20]' with 'struct object_id oid'
cgit.c | 9 +++++----
ui-blob.c | 44 ++++++++++++++++++++++----------------------
ui-commit.c | 8 ++++----
ui-log.c | 2 +-
ui-patch.c | 22 +++++++++++-----------
ui-plain.c | 6 +++---
ui-shared.c | 10 +++++-----
ui-snapshot.c | 18 +++++++++---------
ui-tag.c | 12 ++++++------
ui-tree.c | 6 +++---
10 files changed, 69 insertions(+), 68 deletions(-)
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20160929/21b0c86f/attachment.asc>
reply other threads:[~2016-09-29 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160929222722.64de8fa3@leda.localdomain \
--to=cgit@lists.zx2c4.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).