[no subject]

Наш офисный контакт, 2554 Дороги Кпэлайм Фэйс Фармаки Бет, Ломе, Залив. Международный валютный фонд (МВФ) дает компенсацию всем жертвам жульничества, и Ваш адрес электронной почты был найден в list.this офисе Western Union жертвы жульничества, получил мандат МВФ передать Вашу компенсацию Вам

[no subject]

Наш офисный контакт, 2554 Дороги Кпэлайм Фэйс Фармаки Бет, Ломе, Залив. Международный валютный фонд (МВФ) дает компенсацию всем жертвам жульничества, и Ваш адрес электронной почты был найден в list.this офисе Western Union жертвы жульничества, получил мандат МВФ передать Вашу компенсацию Вам

[no subject]

WU BANK.rtf Description: RTF file

[no subject]

Good Day, I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road Central, Hong Kong. I have a business proposal of $38,980,369.00. All confirmable documents to back up the claims will be made available

Re: [PATCH 4/4] Doc/config.txt: fix documentation for smtpEncryption

astian writes: > Stop saying that smtpEncryption (a configuration variable used by > git-send-email) is not usable in "sendemail." subsections, > because that's false. Hmph, does anybody know when this stopped being true, or was it incorrect from the very beginning? > >

Re: [PATCH 1/4] Doc/config.txt: explain repeated sections

astian writes: > Add a paragraph explaining what happens when a section name is repeated > in the configuration file(s). > > The example configuration file shown in this document already implied > Git's behaviour, this patch simply tries to make it explicit. > > Signed-off-by:

Re: What's cooking in git.git (Jul 2017, #02; Fri, 7)

Kaartic Sivaraam writes: > Just wanted to know something out of curiosity. How am I actually > receiving these "What's cooking" emails though I'm not a subscriber to > the mailing list to which this is being addressed? By having a contribution listed in the

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

René Scharfe writes: > Am 08.07.2017 um 13:08 schrieb Ramsay Jones: >> On 08/07/17 09:58, René Scharfe wrote: >>> Avoid running over the end of another -- a C string whose length we >>> don't know -- by using strcmp(3) instead of memcmp(3) for comparing it >>> with another C

[PATCH 4/4] Doc/config.txt: fix documentation for smtpEncryption

Stop saying that smtpEncryption (a configuration variable used by git-send-email) is not usable in "sendemail." subsections, because that's false. Signed-off-by: astian --- Documentation/config.txt | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH 3/4] Doc/git-send-email.txt: clarify a couple of options

Clarify the meaning of --smtp-encryption and --smtp-server-option. Signed-off-by: astian --- Documentation/git-send-email.txt | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/Documentation/git-send-email.txt

[PATCH 2/4] Doc/config.txt: fix typos

Signed-off-by: astian --- Documentation/config.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index d5c9c4cab..72e85b002 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@

[PATCH 1/4] Doc/config.txt: explain repeated sections

Add a paragraph explaining what happens when a section name is repeated in the configuration file(s). The example configuration file shown in this document already implied Git's behaviour, this patch simply tries to make it explicit. Signed-off-by: astian ---

[PATCH 0/4] Misc. documentation fixes

Hi there, I was looking into adding a new option to git-send-email (and I may later send the patches implementing that) but as I looked over the code and associated documentation I found a few places where I thought improvement could be made. So here are some documentation fixes and

Re: 0 bytes/s vs. ∞ bytes/s

RS> Subject: [PATCH] progress: show overall rate in last update RS> Reported-by: 積丹尼 Dan Jacobson RS> Signed-off-by: Rene Scharfe Thanks!

git-2.13.2: color.branch.local problem

Hi Everyone, When I updated from git-2.10.2 to git-2.13.2 my 'color.branch.local' config setting gets ignored. Corresponding 'remote' or 'current' settings are honored and work as expected Relevant parts of my config file is: [color "branch"] current= reverse local = red bold

[no subject]

Please help me

Re: 0 bytes/s vs. ∞ bytes/s

Am 07.07.2017 um 17:57 schrieb 積丹尼 Dan Jacobson: > Receiving objects: 100% (1003/1003), 1.15 MiB | 0 bytes/s, done. > Receiving objects: 100% (1861/1861), 11.74 MiB | 4.58 MiB/s, done. > Receiving objects: 100% (474/474), 160.72 KiB | 0 bytes/s, done. > Receiving objects: 100% (7190/7190), 26.02

Re: [PATCH] urlmatch: use hex2chr() in append_normalized_escapes()

Am 08.07.2017 um 16:28 schrieb Kyle J. McKay: On Jul 8, 2017, at 01:59, René Scharfe wrote: Simplify the code by using hex2chr() to convert and check for invalid characters at the same time instead of doing that sequentially with one table lookup for each. I think that comment may be a bit

Re: [PATCH] urlmatch: use hex2chr() in append_normalized_escapes()

On Jul 8, 2017, at 01:59, René Scharfe wrote: Simplify the code by using hex2chr() to convert and check for invalid characters at the same time instead of doing that sequentially with one table lookup for each. I think that comment may be a bit misleading as the changes are just switching

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

On Jul 08 2017, René Scharfe wrote: > Am 08.07.2017 um 13:08 schrieb Andreas Schwab: >> On Jul 08 2017, René Scharfe wrote: >> >>> Avoid running over the end of another -- a C string whose length we >>> don't know -- by using strcmp(3) instead of memcmp(3) for

Re: What's cooking in git.git (Jul 2017, #02; Fri, 7)

Just wanted to know something out of curiosity. How am I actually receiving these "What's cooking" emails though I'm not a subscriber to the mailing list to which this is being addressed ? Further, my email address isn't list in the To, Cc or Bcc fields. I wanted to know this as, this has been

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

Am 08.07.2017 um 13:08 schrieb Ramsay Jones: On 08/07/17 09:58, René Scharfe wrote: Avoid running over the end of another -- a C string whose length we don't know -- by using strcmp(3) instead of memcmp(3) for comparing it with another C string. I had to read this twice, along with the patch

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

Am 08.07.2017 um 13:08 schrieb Andreas Schwab: On Jul 08 2017, René Scharfe wrote: Avoid running over the end of another -- a C string whose length we don't know -- by using strcmp(3) instead of memcmp(3) for comparing it with another C string. That's not a good justification

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

On 08/07/17 09:58, René Scharfe wrote: > Avoid running over the end of another -- a C string whose length we > don't know -- by using strcmp(3) instead of memcmp(3) for comparing it > with another C string. I had to read this twice, along with the patch text, before this made any sense. ;-) The

Re: [PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

On Jul 08 2017, René Scharfe wrote: > Avoid running over the end of another -- a C string whose length we > don't know -- by using strcmp(3) instead of memcmp(3) for comparing it > with another C string. That's not a good justification for the change, since memcmp never reads past

[PATCH] wt-status: use separate variable for result of shorten_unambiguous_ref

Store the pointer to the string allocated by shorten_unambiguous_ref in a dedicated variable, short_base, and keep base unchanged. A non-const variable is more appropriate for such an object. It avoids having to cast const away on free and stops redefining the meaning of base, making the code

[PATCH] use DIV_ROUND_UP

Convert code that divides and rounds up to use DIV_ROUND_UP to make the intent clearer and reduce the number of magic constants. Signed-off-by: Rene Scharfe --- builtin/gc.c | 2 +- builtin/grep.c | 2 +- builtin/log.c | 2 +- builtin/receive-pack.c | 2

[PATCH] urlmatch: use hex2chr() in append_normalized_escapes()

Simplify the code by using hex2chr() to convert and check for invalid characters at the same time instead of doing that sequentially with one table lookup for each. Signed-off-by: Rene Scharfe --- urlmatch.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH] sha1_file: add slash once in for_each_file_in_obj_subdir()

Add the slash between loose object subdirectory and file name just once outside the loop instead of overwriting it with each readdir call. Redefine baselen as the length with that slash, and add dirlen for the length without it. The result is slightly less wasteful and can use the the cheaper

[PATCH] apply: use strcmp(3) for comparing strings in gitdiff_verify_name()

Avoid running over the end of another -- a C string whose length we don't know -- by using strcmp(3) instead of memcmp(3) for comparing it with another C string. Signed-off-by: Rene Scharfe --- apply.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/apply.c

Re: [PATCH v5 7/7] fsmonitor: add a performance test

On Fri, Jul 7, 2017 at 8:35 PM, Junio C Hamano wrote: > Ben Peart writes: > >> On 6/14/2017 2:36 PM, Junio C Hamano wrote: >>> Ben Peart writes: >>> > Having said all that, I think you are using this ONLY on windows; > perhaps