Re: [PATCH] l10n: de.po: translate "index" as "Index"

2015-06-01 Thread git
Ralf Thielow venit, vidit, dixit 29.05.2015 20:54: > The term "index" is translated as "Staging-Area" to > not confuse beginners who don't know about Git's index. > > Since the term "staging area" doesn't appear in original > Git messa

Security Alert. You account has been hacked. Password must be need changed.

2018-12-20 Thread git
Hello! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: On moment of hack your account has password: esign You say: this is the old password! Or: I will change my password at any time! Yes! You're right! But the fact is that wh

Security Alert. You account has been hacked. Password must be need changed.

2018-12-20 Thread git
Hello! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: On moment of hack your account has password: callgsm01 You say: this is the old password! Or: I will change my password at any time! Yes! You're right! But the fact is tha

Security Scam Warning.

2018-12-20 Thread git
Hello! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: On moment of hack your account has password: ever You say: this is the old password! Or: I will change my password at any time! Yes! You're right! But the fact is that whe

Your account was under attack! Change your access data!

2019-03-29 Thread git
Hi! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: At the time of hacking your account(git@vger.kernel.org) had this password: whoworg You can say: this is my, but old password! Or: I can change my password at any time! Of

Your account was under attack! Change your access data!

2019-03-29 Thread git
Hi! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: At the time of hacking your account(git@vger.kernel.org) had this password: dirgantara You can say: this is my, but old password! Or: I can change my password at any time! Of

Your account was under attack! Change your access data!

2019-03-29 Thread git
Hi! As you may have noticed, I sent you an email from your account. This means that I have full access to your account: At the time of hacking your account(git@vger.kernel.org) had this password: ani420 You can say: this is my, but old password! Or: I can change my password at any time! Of

High danger. Your account was attacked.

2019-04-17 Thread git
Hi, stranger! I know the usmaniopzxc, this is your password. As you can see, I logged in with your account. And I wrote you this message from your account. If you have already changed your password, my malware will be intercepts it every time. You may not know me, and you are most likely wond

Zdravstvuyte! Vas interesuyut kliyentskiye bazy dannykh?

2019-04-25 Thread git
Zdravstvuyte! Vas interesuyut kliyentskiye bazy dannykh?

Zdravstvujte! Vas interesuyut klientskie bazy dannyh?

2019-08-01 Thread git
Zdravstvujte! Vas interesuyut klientskie bazy dannyh?

Change your password callgsm01 immediately. Your account has been hacked.

2018-11-03 Thread git
I greet you! I have bad news for you. 27/08/2018 - on this day I hacked your operating system and got full access to your account git@vger.kernel.org On that day your account (git@vger.kernel.org) password was: callgsm01 It is useless to change the password, my malware intercepts it every time

Change your password 06239 immediately. Your account has been hacked.

2018-11-06 Thread git
I greet you! I have bad news for you. 27/08/2018 - on this day I hacked your operating system and got full access to your account git@vger.kernel.org On that day your account (git@vger.kernel.org) password was: 06239 It is useless to change the password, my malware intercepts it every time

git@vger.kernel.org - this account has been hacked! Change your password e7d1w8i2n right now!

2018-11-22 Thread git
Hello! I have very bad news for you. 06/08/2018 - on this day I hacked your operating system and got full access to your account git@vger.kernel.org On that day your account git@vger.kernel.org password was: e7d1w8i2n It is useless to change the password, my malware intercepts it every time

[PATCH v7 0/2] json-writer V7

2018-06-05 Thread git
From: Jeff Hostetler Here is V7 of my json-writer patches. Please replace the existing V5/V6 version of jh/json-writer branch with this one. This version cleans up the die()-vs-BUG() issue that Duy mentioned recently. It also fixes a formatting bug when composing empty sub-objects/-arrays. It

[PATCH v7 2/2] json-writer: t0019: add Python unit test

2018-06-05 Thread git
/parse_json_1.py diff --git a/t/t0019-json-writer.sh b/t/t0019-json-writer.sh index c9c2e23..951cd89 100755 --- a/t/t0019-json-writer.sh +++ b/t/t0019-json-writer.sh @@ -233,4 +233,42 @@ test_expect_success 'inline array with no members' ' test_cmp expect actual ' +# As

[PATCH v7 1/2] json_writer: new routines to create data in JSON format

2018-06-05 Thread git
ike format. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the best way to enforce that requirement. For example, on Linx p

[PATCH v8 0/2] json-writer V8

2018-06-07 Thread git
From: Jeff Hostetler Here is V8 of my json-writer patches. Please replace the existing V5/V6/V7 version of the jh/json-writer branch with this one. This version uses perl rather than python to test the generated JSON. Jeff Hostetler (2): json_writer: new routines to create data in JSON forma

[PATCH v8 2/2] json-writer: t0019: add perl unit test

2018-06-07 Thread git
100644 t/t0019/parse_json.perl diff --git a/t/t0019-json-writer.sh b/t/t0019-json-writer.sh index c9c2e23..fd61fe4 100755 --- a/t/t0019-json-writer.sh +++ b/t/t0019-json-writer.sh @@ -233,4 +233,42 @@ test_expect_success 'inline array with no members' ' test_cmp expect actu

[PATCH v8 1/2] json_writer: new routines to create data in JSON format

2018-06-07 Thread git
ike format. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the best way to enforce that requirement. For example, on Linx p

[RFC PATCH v1] telemetry design overview (part 1)

2018-06-07 Thread git
From: Jeff Hostetler I've been working to add code to Git to optionally collect telemetry data. The goal is to be able to collect performance data from Git commands and allow it to be aggregated over a user community to find "slow commands". I'm going to break this up into

[RFC PATCH v1] telemetry: design documenation

2018-06-07 Thread git
diff --git a/Documentation/technical/telemetry.txt b/Documentation/technical/telemetry.txt new file mode 100644 index 000..0a708ad --- /dev/null +++ b/Documentation/technical/telemetry.txt @@ -0,0 +1,475 @@ +Telemetry Design Notes +== + +The telemetry feature allows Git to

[PATCH v9] json_writer V9

2018-06-12 Thread git
From: Jeff Hostetler Here is V9 of my json-writer patches. Please replace the existing V5..V8 versions with this one. This version has been rebased onto v2.18.0-rc1 rather than 2.17 because of changes to the test-tool setup. I've incorporated all of the suggestions on the V8 version, including

[PATCH v9] json_writer: new routines to create JSON data

2018-06-12 Thread git
for output. It does not attempt to build an object model of the JSON data. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the

[PATCH v10] json_writer V10

2018-06-13 Thread git
From: Jeff Hostetler Here is V10 of my json-writer patch. I fixed the DEVELOPER=1 warnings that Eric pointed out and refactored the indent_pretty() code as Junio suggested. Jeff Hostetler (1): json_writer: new routines to create JSON data Makefile| 2 + json-writer.c

[PATCH v10] json_writer: new routines to create JSON data

2018-06-13 Thread git
for output. It does not attempt to build an object model of the JSON data. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the

[PATCH v11] json_writer V10

2018-07-13 Thread git
From: Jeff Hostetler Here is V11 of my json-writer patch. I fixed a minor initialization bug in V10 and rebased it onto v2.18.0 (from an 2.18.0-RC version). Jeff Hostetler (1): json_writer: new routines to create JSON data Makefile| 2 + json-writer.c | 4

[PATCH v11] json_writer: new routines to create JSON data

2018-07-13 Thread git
for output. It does not attempt to build an object model of the JSON data. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the

[PATCH v1 04/25] structured-logging: add session-id to log events

2018-07-13 Thread git
From: Jeff Hostetler Teach git to create a unique session id (SID) during structured logging initialization and use that SID in all log events. This SID is exported into a transient environment variable and inherited by child processes. This allows git child processes to be related back to the

[PATCH v1 00/25] RFC: structured logging

2018-07-13 Thread git
From: Jeff Hostetler This RFC patch series adds structured logging to git. The motivation, background, and limitations of this feature are described at the beginning of the design document in the first commit. The design document also contains a section comparing this feature with the existing

[PATCH v1 02/25] structured-logging: add STRUCTURED_LOGGING=1 to Makefile

2018-07-13 Thread git
insertions(+) create mode 100644 structured-logging.c create mode 100644 structured-logging.h diff --git a/Makefile b/Makefile index 39ca66b..ccc39bf 100644 --- a/Makefile +++ b/Makefile @@ -442,6 +442,8 @@ all:: # When cross-compiling, define HOST_CPU as the canonical name of the CPU on # which

[PATCH v1 01/25] structured-logging: design document

2018-07-13 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- Documentation/technical/structured-logging.txt | 816 + 1 file changed, 816 insertions(+) create mode 100644 Documentation/technical/structured-logging.txt diff --git a/Documentation/technical/structured

[PATCH v1 06/25] structured-logging: set sub_command field for checkout command

2018-07-13 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- builtin/checkout.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/builtin/checkout.c b/builtin/checkout.c index 2e1d237..d05890b 100644 --- a/builtin/checkout.c +++ b/builtin/checkout.c @@ -249,6 +249,8 @@ static int

[PATCH v1 21/25] structured-logging: add detail-events for child processes

2018-07-13 Thread git
From: Jeff Hostetler Teach git to emit "detail" events with category "child" before a child process is started and after it finishes. These events can be used to infer time spent by git waiting for child processes to complete. These events are controlled by the slog.detail

[PATCH v1 25/25] structured-logging: add config data facility

2018-07-13 Thread git
g of the log. Knowing the filter settings can help post-processors reason about the contents of the log. Signed-off-by: Jeff Hostetler --- structured-logging.c | 132 +++ structured-logging.h | 13 +++++ 2 files changed, 145 insertions(+) diff --git a

[PATCH v1 13/25] structured-logging: add timer around wt-status functions

2018-07-13 Thread git
t-status.c | 20 1 file changed, 20 insertions(+) diff --git a/wt-status.c b/wt-status.c index d1c0514..f663a37 100644 --- a/wt-status.c +++ b/wt-status.c @@ -580,8 +580,11 @@ static void wt_status_collect_updated_cb(struct diff_queue_struct *q, s

[PATCH v1 24/25] structured-logging: t0420 tests for interacitve child_summary

2018-07-13 Thread git
From: Jeff Hostetler Test running a command with a fake pager and verify that a child_summary is generated. Signed-off-by: Jeff Hostetler --- t/t0420-structured-logging.sh | 30 ++ 1 file changed, 30 insertions(+) diff --git a/t/t0420-structured-logging.sh b/t

[PATCH v1 12/25] structured-logging: add timer around do_write_index

2018-07-13 Thread git
From: Jeff Hostetler Use a SLOG timer to record the time spend in do_write_index() and report it in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- read-cache.c | 5 + 1 file changed, 5 insertions(+) diff --git a/read-cache.c b/read-cache.c index df5dc87..7fe66b5 10

[PATCH v1 15/25] structured-logging: t0420 tests for timers

2018-07-13 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- t/t0420-structured-logging.sh | 48 +++ 1 file changed, 48 insertions(+) diff --git a/t/t0420-structured-logging.sh b/t/t0420-structured-logging.sh index a594af3..37c7e83 100755 --- a/t/t0420

[PATCH v1 17/25] structured-logging: add aux-data for index size

2018-07-13 Thread git
From: Jeff Hostetler Teach do_read_index() and do_write_index() to record the size of the index in aux-data. This will be reported in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- read-cache.c | 4 1 file changed, 4 insertions(+) diff --git a/read-cache.c b/read-cac

[PATCH v1 10/25] structured-logging: add timer facility

2018-07-13 Thread git
From: Jeff Hostetler Add timer facility to structured logging. This allows stopwatch-like operations over the life of the git process. Timer data is summarized in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- Documentation/config.txt | 6 ++ structured-logging.c

[PATCH v1 22/25] structured-logging: add child process classification

2018-07-13 Thread git
From: Jeff Hostetler Teach git to classify child processes as "editor", "pager", "subprocess", "alias", "shell", or "other". Add the child process classification to the child detail events. Mark child processes of class "editor

[PATCH v1 08/25] structured-logging: add detail-event facility

2018-07-13 Thread git
g.txt | 13 +++ structured-logging.c | 95 structured-logging.h | 16 3 files changed, 124 insertions(+) diff --git a/Documentation/config.txt b/Documentation/config.txt index c79f2bf..88f93fe 100644 --- a/Documentation/config

[PATCH v1 07/25] structured-logging: t0420 basic tests

2018-07-13 Thread git
| 52 +++ t/test-lib.sh | 1 + 3 files changed, 196 insertions(+) create mode 100755 t/t0420-structured-logging.sh create mode 100644 t/t0420/parse_json.perl diff --git a/t/t0420-structured-logging.sh b/t/t0420-structured-logging.sh new file mode 100755 index 00

[PATCH v1 14/25] structured-logging: add timer around preload_index

2018-07-13 Thread git
From: Jeff Hostetler Use a SLOG timer to record the time spend in preload_index() and report it in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- preload-index.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/preload-index.c b/preload-index.c index 4d08d44..572b

[PATCH v1 11/25] structured-logging: add timer around do_read_index

2018-07-13 Thread git
From: Jeff Hostetler Use a SLOG timer to record the time spent in do_read_index() and report it in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- read-cache.c | 5 + 1 file changed, 5 insertions(+) diff --git a/read-cache.c b/read-cache.c index 3725882..df5dc87 100644

[PATCH v1 18/25] structured-logging: add aux-data for size of sparse-checkout file

2018-07-13 Thread git
From: Jeff Hostetler Teach unpack_trees() to record the number of entries in the sparse-checkout file in the aux-data. This will be reported in the "cmd_exit" event. Signed-off-by: Jeff Hostetler --- unpack-trees.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --gi

[PATCH v1 23/25] structured-logging: t0420 tests for child process detail events

2018-07-13 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- t/t0420-structured-logging.sh | 39 +++ 1 file changed, 39 insertions(+) diff --git a/t/t0420-structured-logging.sh b/t/t0420-structured-logging.sh index 2e06cd7..4ac404d 100755 --- a/t/t0420-structured

[PATCH v1 19/25] structured-logging: t0420 tests for aux-data

2018-07-13 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- t/t0420-structured-logging.sh | 33 + 1 file changed, 33 insertions(+) diff --git a/t/t0420-structured-logging.sh b/t/t0420-structured-logging.sh index 37c7e83..2e06cd7 100755 --- a/t/t0420-structured

[PATCH v1 03/25] structured-logging: add structured logging framework

2018-07-13 Thread git
From: Jeff Hostetler Teach git to optionally generate structured logging data in JSON using the json-writer API. "cmd_start" and "cmd_end" events are generated. Structured logging is only available when git is built with STRUCTURED_LOGGING=1. Structured logging is only ena

[PATCH v1 16/25] structured-logging: add aux-data facility

2018-07-13 Thread git
| 116 +++ structured-logging.h | 21 + 3 files changed, 143 insertions(+) diff --git a/Documentation/config.txt b/Documentation/config.txt index 7817966..ca78d4c 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -3195,6 +3195,12 @@ s

[PATCH v1 20/25] structured-logging: add structured logging to remote-curl

2018-07-13 Thread git
--- remote-curl.c | 16 +++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/remote-curl.c b/remote-curl.c index 99b0bed..ed910f8 100644 --- a/remote-curl.c +++ b/remote-curl.c @@ -1322,8 +1322,9 @@ static int stateless_connect(const char *service_name) return 0

[PATCH v1 05/25] structured-logging: set sub_command field for branch command

2018-07-13 Thread git
From: Jeff Hostetler Set sub-command field for the various forms of the branch command. Signed-off-by: Jeff Hostetler --- builtin/branch.c | 8 1 file changed, 8 insertions(+) diff --git a/builtin/branch.c b/builtin/branch.c index 5217ba3..fba516f 100644 --- a/builtin/branch.c +++ b

[PATCH v1 09/25] structured-logging: add detail-event for lazy_init_name_hash

2018-07-13 Thread git
From: Jeff Hostetler Teach git to generate a structured logging detail-event for lazy_init_name_hash(). This is marked as an "index" category event and includes time and size data for the hashmaps. Signed-off-by: Jeff Hostetler --- name-hash.c | 26 ++ 1 fi

[PATCH v1] msvc: fix non-standard escape sequence in source

2018-07-24 Thread git
quot; sequence is an extension supported by GCC, clang, and tcc. [1] https://en.wikipedia.org/wiki/Escape_sequences_in_C Signed-off-by: Jeff Hostetler --- convert.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/convert.c b/convert.c index 56cfe31..52092be 100644 --- a/co

[PATCH v1] config.c: fix msvc compile error

2018-07-24 Thread git
array. Signed-off-by: Jeff Hostetler --- builtin/config.c | 79 1 file changed, 40 insertions(+), 39 deletions(-) diff --git a/builtin/config.c b/builtin/config.c index b29d26d..564f18f 100644 --- a/builtin/config.c +++ b/builtin/config.c

Keep your secrets safe!

2019-08-15 Thread git
Hello! I am a representative of the ChaosCC hacker group. In the period from 23/06/2019 to 11/08/2019 we got access to your account git@vger.kernel.org by hacking one of the domain.com mail servers. Your pass for above account on moment of hack was: e1ysha You already changed the password

Keep your secrets safe!

2019-08-16 Thread git
Hello! I am a representative of the ChaosCC hacker group. In the period from 23/06/2019 to 11/08/2019 we got access to your account git@vger.kernel.org by hacking one of the domain.com mail servers. Your pass for above account on moment of hack was: bread4u2d You already changed the password

Keep your secrets safe!

2019-08-16 Thread git
Hello! I am a representative of the ChaosCC hacker group. In the period from 23/06/2019 to 11/08/2019 we got access to your account git@vger.kernel.org by hacking one of the domain.com mail servers. Your pass for above account on moment of hack was: 28121971 You already changed the password

[PATCH 2/2] json-writer: unit test

2018-03-16 Thread git
create mode 100755 t/t0019-json-writer.sh diff --git a/Makefile b/Makefile index 9000369..57f58e6 100644 --- a/Makefile +++ b/Makefile @@ -662,6 +662,7 @@ TEST_PROGRAMS_NEED_X += test-fake-ssh TEST_PROGRAMS_NEED_X += test-genrandom TEST_PROGRAMS_NEED_X += test-hashmap TEST_PROGRAMS_NEED_X

[PATCH 1/2] json_writer: new routines to create data in JSON format

2018-03-16 Thread git
insertions(+) create mode 100644 json-writer.c create mode 100644 json-writer.h diff --git a/Makefile b/Makefile index 1a9b23b..9000369 100644 --- a/Makefile +++ b/Makefile @@ -815,6 +815,7 @@ LIB_OBJS += hashmap.o LIB_OBJS += help.o LIB_OBJS += hex.o LIB_OBJS += ident.o +LIB_OBJS += json-writer.o

[PATCH 0/2] routines to generate JSON data

2018-03-16 Thread git
ever.) Documentation for the new API is given in json-writer.h at the bottom of the first patch. I wasn't sure how to unit test the API from a shell script, so I added a helper command that does most of the work in the second patch. [1] https://public-inbox.org/git/20180313004940.gg61...@goog

Odkaz ze stránek http://www.pojistenispektrum.cz

2018-03-17 Thread git
Pan/paní Only the best on dating site URL http://bit.ly/2EjyKcY Vám zasílá odkaz na stránku ze serveru http://www.pojistenispektrum.cz, která by Vás mohla zajímat: http://bit.ly/2EjyKcY

[PATCH v2] json_writer: new routines to create data in JSON format

2018-03-21 Thread git
t/t0019-json-writer.sh | 102 +++ 5 files changed, 931 insertions(+) create mode 100644 json-writer.c create mode 100644 json-writer.h create mode 100644 t/helper/test-json-writer.c create mode 100755 t/t0019-json-writer.sh diff --git a

[PATCH v2] routines to generate JSON data

2018-03-21 Thread git
are UCS2/UTF-16 in the filesystem and we always convert to/from UTF-8 when moving between git data structures and IO calls. There are few other fields (like author name) that we may want to log which may or may not be, but that is beyond our control. Even localized error messages may be prob

[PATCH v3] routines to generate JSON data

2018-03-23 Thread git
JSON-like format. I say "JSON-like" because we don't enforce the Unicode/UTF-8 requirement [3,4] on string values. This was discussed on the mailing list in the [v1] and [v2] threads, but to summarize here: Git doesn't know if various fields, such as Unix pathnames and author n

[PATCH v3] json_writer: new routines to create data in JSON format

2018-03-23 Thread git
diff --git a/Makefile b/Makefile index 1a9b23b..57f58e6 100644 --- a/Makefile +++ b/Makefile @@ -662,6 +662,7 @@ TEST_PROGRAMS_NEED_X += test-fake-ssh TEST_PROGRAMS_NEED_X += test-genrandom TEST_PROGRAMS_NEED_X += test-hashmap TEST_PROGRAMS_NEED_X += test-index-version +TEST_PROGRAMS_NEED_X

Re: [PATCH v2] branch: implement shortcut to delete last branch

2018-03-26 Thread git
Thanks for Cc-ing me, and sorry for not being very responsive these days :-\. Jeff King writes: > On Fri, Mar 23, 2018 at 10:40:34PM +, Aaron Greenberg wrote: > >> I can appreciate Matthieu's points on the use of "-" in destructive >> commands. As of thi

[PATCH v4] routines to generate JSON data

2018-03-26 Thread git
From: Jeff Hostetler This is version 4 of my JSON data format routines. This version adds a "pretty" formatted output. I consider this to be mainly for debugging, but worth keeping available in release builds. I simplified the stack-level tracing as suggested by René Scharfe and hinted at by P

[PATCH v4] json_writer: new routines to create data in JSON format

2018-03-26 Thread git
ike format. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the best way to enforce that requirement. For example, on Linx p

[PATCH v5] json_writer: new routines to create data in JSON format

2018-03-27 Thread git
ike format. We say "JSON-like" because we do not enforce the Unicode (usually UTF-8) requirement on string fields. Internally, Git does not necessarily have Unicode/UTF-8 data for most fields, so it is currently unclear the best way to enforce that requirement. For example, on Linx p

[PATCH v5] routines to generate JSON data

2018-03-27 Thread git
patch. https://github.com/jeffhostetler/git/pull/11 Jeff Hostetler (1): json_writer: new routines to create data in JSON format Makefile| 2 + json-writer.c | 394 ++ json-writer.h | 91 +++ t/helper/test-json

[PATCH v6] json-writer: fixups for V5

2018-03-28 Thread git
++-- 2 files changed, 20 insertions(+), 20 deletions(-) diff --git a/json-writer.c b/json-writer.c index 1b49158..dbfcf70 100644 --- a/json-writer.c +++ b/json-writer.c @@ -165,7 +165,7 @@ void jw_object_string(struct json_writer *jw, const char *key, const char *value

[PATCH v9 0/3] read-cache: speed up add_index_entry

2017-04-11 Thread git
From: Jeff Hostetler Version 9 addresses the following: () p0006 perf test can now run using either synthetic repos from t/perf/repos/many-repos.sh -OR- an actual real-world repo. () The commit message has been updated to include results of p0006 on linux.git. () Line 0006.3

[PATCH v9 1/3] read-cache: add strcmp_offset function

2017-04-11 Thread git
--git a/Makefile b/Makefile index 9ec6065..4c4c246 100644 --- a/Makefile +++ b/Makefile @@ -631,6 +631,7 @@ TEST_PROGRAMS_NEED_X += test-scrap-cache-tree TEST_PROGRAMS_NEED_X += test-sha1 TEST_PROGRAMS_NEED_X += test-sha1-array TEST_PROGRAMS_NEED_X += test-sigchain +TEST_PROGRAMS_NEED_X += test

[PATCH v9 2/3] p0006-read-tree-checkout: perf test to time read-tree

2017-04-11 Thread git
t/perf/p0006-read-tree-checkout.sh create mode 100644 t/perf/repos/.gitignore create mode 100755 t/perf/repos/many-files.sh diff --git a/t/perf/p0006-read-tree-checkout.sh b/t/perf/p0006-read-tree-checkout.sh new file mode 100755 index 000..5881251 --- /dev/null +++ b/t/perf/p0006-read-tree

[PATCH v9 3/3] read-cache: speed up add_index_entry during checkout

2017-04-11 Thread git
) 0.50(0.34+0.18) -15.3% 0006.5: switch between aliases (57994)0.62(0.48+0.16) 0.50(0.35+0.16) -19.4% Signed-off-by: Jeff Hostetler --- read-cache.c | 46 -- 1 file changed, 44 insertions(+), 2 deletions(-) diff --git a/read

[PATCH v4 2/2] p0005-status: time status on very large repo

2017-04-11 Thread git
From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- t/perf/p0005-status.sh | 51 ++ 1 file changed, 51 insertions(+) create mode 100755 t/perf/p0005-status.sh diff --git a/t/perf/p0005-status.sh b/t/perf/p0005-status.sh new file mode 100755

[PATCH v4 1/2] string-list: use ALLOC_GROW macro when reallocing string_list

2017-04-11 Thread git
(-) diff --git a/string-list.c b/string-list.c index 45016ad..003ca18 100644 --- a/string-list.c +++ b/string-list.c @@ -41,10 +41,7 @@ static int add_entry(int insert_at, struct string_list *list, const char *string if (exact_match) return -1 - index; - if (list->

[PATCH v4 0/2] string-list: use ALLOC_GROW macro when reallocing

2017-04-11 Thread git
From: Jeff Hostetler Version 4 greatly simplifies the p0005 perf test. It now uses an existing repo -- either real-world or artificial from t/perf/repos/many-files.sh. Jeff Hostetler (2): string-list: use ALLOC_GROW macro when reallocing string_list p0005-status: time status on very large re

[PATCH v3] unpack-trees: avoid duplicate ODB lookups during checkout

2017-04-13 Thread git
-trees.c | 37 + 1 file changed, 33 insertions(+), 4 deletions(-) diff --git a/unpack-trees.c b/unpack-trees.c index 3a8ee19..a674423 100644 --- a/unpack-trees.c +++ b/unpack-trees.c @@ -531,6 +531,11 @@ static int switch_cache_bottom(struct traverse_info *info

[PATCH v3] unpack-trees: avoid duplicate ODB lookups during checkout

2017-04-13 Thread git
From: Jeff Hostetler Version 3 uses a structure copy rather than memcpy and adds a comment. Jeff Hostetler (1): unpack-trees: avoid duplicate ODB lookups during checkout unpack-trees.c | 37 + 1 file changed, 33 insertions(+), 4 deletions(-) -- 2.9.3

[PATCH v10 0/3] read-cache: speed up add_index_entry

2017-04-14 Thread git
From: Jeff Hostetler Version 10 addresses mailing list comments on coding style in read-cache.c and in p0006. I've also adjusted the speed-up algorithm and more thoroughly documented the cases in the code. We skip the binary searches whenever we can prove that the new entry (and every sub-direc

[PATCH v10 2/3] p0006-read-tree-checkout: perf test to time read-tree

2017-04-14 Thread git
/perf/p0006-read-tree-checkout.sh create mode 100644 t/perf/repos/.gitignore create mode 100755 t/perf/repos/many-files.sh diff --git a/t/perf/p0006-read-tree-checkout.sh b/t/perf/p0006-read-tree-checkout.sh new file mode 100755 index 000..78cc23f --- /dev/null +++ b/t/perf/p0006-read-tree

[PATCH v10 1/3] read-cache: add strcmp_offset function

2017-04-14 Thread git
--git a/Makefile b/Makefile index 9ec6065..4c4c246 100644 --- a/Makefile +++ b/Makefile @@ -631,6 +631,7 @@ TEST_PROGRAMS_NEED_X += test-scrap-cache-tree TEST_PROGRAMS_NEED_X += test-sha1 TEST_PROGRAMS_NEED_X += test-sha1-array TEST_PROGRAMS_NEED_X += test-sigchain +TEST_PROGRAMS_NEED_X += test

[PATCH v10 3/3] read-cache: speed up add_index_entry during checkout

2017-04-14 Thread git
--git a/read-cache.c b/read-cache.c index 97f13a1..ba95fbb 100644 --- a/read-cache.c +++ b/read-cache.c @@ -910,6 +910,9 @@ int strcmp_offset(const char *s1, const char *s2, size_t *first_change) /* * Do we have another file with a pathname that is a proper * subset of the name we're tryi

[PATCH v4] unpack-trees: avoid duplicate ODB lookups during checkout

2017-04-14 Thread git
-trees.c | 38 +- 1 file changed, 33 insertions(+), 5 deletions(-) diff --git a/unpack-trees.c b/unpack-trees.c index 3a8ee19..07b0f11 100644 --- a/unpack-trees.c +++ b/unpack-trees.c @@ -531,12 +531,18 @@ static int switch_cache_bottom(struct traverse_info *info

[PATCH v4] unpack-trees: avoid duplicate ODB lookups during checkout

2017-04-14 Thread git
From: Jeff Hostetler Version 4 cleans up the buf[] allocation and freeing as suggested on the mailing list. Jeff Hostetler (1): unpack-trees: avoid duplicate ODB lookups during checkout unpack-trees.c | 38 +- 1 file changed, 33 insertions(+), 5 deletions(

[PATCH v5] string-list: use ALLOC_GROW macro when reallocing string_list

2017-04-14 Thread git
+ 2 files changed, 50 insertions(+), 4 deletions(-) create mode 100755 t/perf/p0005-status.sh diff --git a/string-list.c b/string-list.c index 45016ad..003ca18 100644 --- a/string-list.c +++ b/string-list.c @@ -41,10 +41,7 @@ static int add_entry(int

[PATCH v5] string-list: use ALLOC_GROW macro when reallocing

2017-04-14 Thread git
From: Jeff Hostetler Version 5 addresses coding style comments from the mailing list in the perf test and squashes the changes into 1 commit. Jeff Hostetler (1): string-list: use ALLOC_GROW macro when reallocing string_list string-list.c | 5 + t/perf/p0005-status.sh | 49 +

[PATCH v7] read-cache: call verify_hdr() in a background thread

2017-04-14 Thread git
From: Jeff Hostetler Version 7 of this patch cleans up the fsck test using test_when_finished and eliminates unnecessary mv/rm's. Jeff Hostetler (1): read-cache: force_verify_index_checksum builtin/fsck.c | 1 + cache.h | 2 ++ read-cache.c| 7 +++ t/t1450-fsck.sh | 13 ++

[PATCH v7] read-cache: force_verify_index_checksum

2017-04-14 Thread git
From: Jeff Hostetler Teach git to skip verification of the SHA1-1 checksum at the end of the index file in verify_hdr() which is called from read_index() unless the "force_verify_index_checksum" global variable is set. Teach fsck to force this verification. The checksum verificat

[PATCH v11 3/5] read-cache: speed up add_index_entry during checkout

2017-04-17 Thread git
lookups per file. This preserves the original behavior but simply checks the last element before starting the search. This helps performance on very large repositories. Signed-off-by: Jeff Hostetler --- read-cache.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/read

[PATCH v11 0/5] read-cache: speed up add_index_entry

2017-04-17 Thread git
From: Jeff Hostetler Version 11 splits the changes in read-cache.c into 3 commits so that they can be independently evaluated. And adds subscript guard for istate->cache_nr > 0 which might be necessary if remove_index_entry_at() deletes the only entry in the array. Jeff Hostetler (5): read-cac

[PATCH v11 1/5] read-cache: add strcmp_offset function

2017-04-17 Thread git
--git a/Makefile b/Makefile index 9ec6065..4c4c246 100644 --- a/Makefile +++ b/Makefile @@ -631,6 +631,7 @@ TEST_PROGRAMS_NEED_X += test-scrap-cache-tree TEST_PROGRAMS_NEED_X += test-sha1 TEST_PROGRAMS_NEED_X += test-sha1-array TEST_PROGRAMS_NEED_X += test-sigchain +TEST_PROGRAMS_NEED_X += test

[PATCH v11 5/5] read-cache: speed up has_dir_name (part 2)

2017-04-17 Thread git
-directory prefix. The net-net gains for add_index_entry_with_check() and both had_dir_name() commits are best seen for very large repos. Here are results for a synthetic repo with 4.2M files. $ GIT_PERF_REPO=~/work/gfw/t/perf/repos/gen-many-files-10.4.3.git/ ./run HEAD~3 HEAD ./p0006-read-tree

[PATCH v11 4/5] read-cache: speed up has_dir_name (part 1)

2017-04-17 Thread git
. Signed-off-by: Jeff Hostetler --- read-cache.c | 45 + 1 file changed, 45 insertions(+) diff --git a/read-cache.c b/read-cache.c index 6a27688..9af0bd4 100644 --- a/read-cache.c +++ b/read-cache.c @@ -910,6 +910,9 @@ int strcmp_offset(const char *s1

[PATCH v11 2/5] p0006-read-tree-checkout: perf test to time read-tree

2017-04-17 Thread git
/perf/p0006-read-tree-checkout.sh create mode 100644 t/perf/repos/.gitignore create mode 100755 t/perf/repos/many-files.sh diff --git a/t/perf/p0006-read-tree-checkout.sh b/t/perf/p0006-read-tree-checkout.sh new file mode 100755 index 000..78cc23f --- /dev/null +++ b/t/perf/p0006-read-tree

[PATCH v1] diffcore-rename speedup

2017-04-18 Thread git
From: Jeff Hostetler Here is another micro-optimization for very large repositories. Speed up register_rename_src() in diffcore-rename.c Jeff Hostetler (1): diffcore-rename: speed up register_rename_src diffcore-rename.c | 13 + 1 file changed, 13 insertions(+) -- 2.9.3

[PATCH v1] diffcore-rename: speed up register_rename_src

2017-04-18 Thread git
anged, 13 insertions(+) diff --git a/diffcore-rename.c b/diffcore-rename.c index f7444c8..543a409 100644 --- a/diffcore-rename.c +++ b/diffcore-rename.c @@ -81,6 +81,18 @@ static struct diff_rename_src *register_rename_src(struct diff_filepair *p) first = 0; last = rename_s

[PATCH v12 2/5] p0006-read-tree-checkout: perf test to time read-tree

2017-04-19 Thread git
100644 t/perf/repos/.gitignore create mode 100755 t/perf/repos/inflate-repo.sh create mode 100755 t/perf/repos/many-files.sh diff --git a/t/perf/p0006-read-tree-checkout.sh b/t/perf/p0006-read-tree-checkout.sh new file mode 100755 index 000..78cc23f --- /dev/null +++ b/t/perf/p0006-read-tree

  1   2   3   >