From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: [PATCH 0/4] rename "sha1-foo" files
Date: Wed, 30 Dec 2020 00:52:56 +0100 [thread overview]
Message-ID: <cover.1609282997.git.martin.agren@gmail.com> (raw)
We have some source files with filenames such as sha1-lookup.c and
sha1-name.c containing a few variable names, comments and the like
referencing "sha1". But they are able to handle SHA-256 as well. Here's
my attempt at removing "sha1" from the contents and names of these
files.
Martin Ågren (4):
object-name.c: rename from sha1-name.c
object-file.c: rename from sha1-file.c
sha1-lookup: rename `sha1_pos()` as `hash_pos()`
hash-lookup: rename from sha1-lookup
t/oid-info/README | 2 +-
sha1-lookup.h => hash-lookup.h | 14 +++++++-------
bisect.c | 2 +-
builtin/index-pack.c | 2 +-
builtin/name-rev.c | 4 ++--
commit-graph.c | 8 ++++----
commit.c | 4 ++--
sha1-lookup.c => hash-lookup.c | 22 +++++++++++-----------
list-objects-filter.c | 2 +-
midx.c | 2 +-
sha1-file.c => object-file.c | 4 ++--
sha1-name.c => object-name.c | 14 +++++++-------
oid-array.c | 4 ++--
pack-bitmap-write.c | 4 ++--
packfile.c | 2 +-
patch-ids.c | 2 +-
rerere.c | 4 ++--
Makefile | 6 +++---
18 files changed, 51 insertions(+), 51 deletions(-)
rename sha1-lookup.h => hash-lookup.h (72%)
rename sha1-lookup.c => hash-lookup.c (84%)
rename sha1-file.c => object-file.c (99%)
rename sha1-name.c => object-name.c (99%)
--
2.30.0
next reply other threads:[~2020-12-29 23:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 23:52 Martin Ågren [this message]
2020-12-29 23:52 ` [PATCH 1/4] object-name.c: rename from sha1-name.c Martin Ågren
2020-12-30 1:19 ` Derrick Stolee
2020-12-29 23:52 ` [PATCH 2/4] object-file.c: rename from sha1-file.c Martin Ågren
2020-12-29 23:52 ` [PATCH 3/4] sha1-lookup: rename `sha1_pos()` as `hash_pos()` Martin Ågren
2020-12-30 1:21 ` Derrick Stolee
2020-12-29 23:53 ` [PATCH 4/4] hash-lookup: rename from sha1-lookup Martin Ågren
2020-12-30 1:29 ` [PATCH 0/4] rename "sha1-foo" files Derrick Stolee
2020-12-30 8:01 ` Martin Ågren
2020-12-30 13:35 ` Derrick Stolee
2020-12-30 4:22 ` brian m. carlson
2020-12-30 8:04 ` Martin Ågren
2020-12-31 11:56 ` [PATCH v2 " Martin Ågren
2020-12-31 11:56 ` [PATCH v2 1/4] object-name.c: rename from sha1-name.c Martin Ågren
2020-12-31 11:56 ` [PATCH v2 2/4] object-file.c: rename from sha1-file.c Martin Ågren
2020-12-31 11:56 ` [PATCH v2 3/4] sha1-lookup: rename `sha1_pos()` as `hash_pos()` Martin Ågren
2020-12-31 11:56 ` [PATCH v2 4/4] hash-lookup: rename from sha1-lookup Martin Ågren
2020-12-31 12:47 ` [PATCH v2 0/4] rename "sha1-foo" files Derrick Stolee
2020-12-31 13:36 ` Martin Ågren
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=cover.1609282997.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.