[PATCH v2] zsh: complete unquoted paths with spaces correctly

2018-12-29 Thread Chayoung You
The following is the description of -Q flag of zsh compadd [1]: This flag instructs the completion code not to quote any metacharacters in the words when inserting them into the command line. Let's say there is a file named 'foo bar.txt' in repository, but it's not yet added to the re

Re: Lack of debug info from git commit -vvv -S -am "..."

2018-12-29 Thread Duy Nguyen
On Sun, Dec 30, 2018 at 7:38 AM Jeffrey Walton wrote: > > I'm trying to determine why a new installation of GnuPG is having > trouble. The new install is in /usr/local. The other install is from > the distro and is OK. > > Here's the new installation error message: > > $ git commit -vvv -S -am

Re: [PATCH 0/2] Improve documentation on UTF-16

2018-12-29 Thread brian m. carlson
On Fri, Dec 28, 2018 at 09:46:18AM +0100, Ævar Arnfjörð Bjarmason wrote: > > On Thu, Dec 27 2018, brian m. carlson wrote: > > > We've recently fielded several reports from unhappy Windows users about > > our handling of UTF-16, UTF-16LE, and UTF-16BE, none of which seem to be > > suitable for cer

Git Test Coverage Report (Saturday, Dec 29)

2018-12-29 Thread Derrick Stolee
Here is today's test coverage report. Thanks, -Stolee [1] https://dev.azure.com/git/git/_build/results?buildId=289 --- pu: e31bc98f4bb8c7cf2a943a3b3b3de69a34a4349c jch: 5442582aa4fe91238d2c294660d08fc1e0efc8b7 next: 81188d93c3fce477216ba905bd37ab453a74b11d master: b21ebb671bb7dea8d342225f0d6

Lack of debug info from git commit -vvv -S -am "..."

2018-12-29 Thread Jeffrey Walton
I'm trying to determine why a new installation of GnuPG is having trouble. The new install is in /usr/local. The other install is from the distro and is OK. Here's the new installation error message: $ git commit -vvv -S -am "Update GnuPG recipe" error: gpg failed to sign the data fat

[PATCH 1/2] t5403: simplify by using a single repository

2018-12-29 Thread orgads
From: Orgad Shaneh There is no strong reason to use separate clones to run these tests; just use a single test repository prepared with more modern test_commit shell helper function. While at it, replace three "awk '{print $N}'" on the same file with shell built-in "read" into three variables.

[PATCH 2/2] Rebase: Run post-checkout hook on checkout

2018-12-29 Thread orgads
From: Orgad Shaneh The scripted version of rebase used to run this hook on the initial checkout. The transition to built-in introduced a regression. Signed-off-by: Orgad Shaneh --- builtin/rebase.c | 12 ++-- t/t5403-post-checkout-hook.sh | 20 2 files

Re: [PATCH 1/2] t5403: Refactor

2018-12-29 Thread Orgad Shaneh
On Sat, Dec 29, 2018 at 12:34 AM Junio C Hamano wrote: > > org...@gmail.com writes: > > > Subject: Re: [PATCH 1/2] t5403: Refactor > > Hmph. "Refactor" alone leaves readers wondering "refactor what?", > "refactor for what?" and "refactor how?". Given that the overfall > goal this change seeks se

Re: [PATCH 2/2] Rebase: Run post-checkout hook on checkout

2018-12-29 Thread Orgad Shaneh
On Sat, Dec 29, 2018 at 12:53 AM Junio C Hamano wrote: > > org...@gmail.com writes: > > > From: Orgad Shaneh > > > Re: [PATCH 2/2] Rebase: Run post-checkout hook on checkout > > There is no explanation here? > > Is this a regression fix (i.e. scripted version of "rebase" used to > run the hook)?

[PATCH v2 0/2] Accept error packets in any context

2018-12-29 Thread Masaya Suzuki
This makes it possible for servers to send an error message back to clients in an arbitrary situation. The first patch was originally sent in [1]. This version includes some fix. The second patch was originally sent in [2]. Later, this was cherry-picked in [3]. In the discussion in [3], we agreed

[PATCH v2 2/2] pack-protocol.txt: accept error packets in any context

2018-12-29 Thread Masaya Suzuki
In the Git pack protocol definition, an error packet may appear only in a certain context. However, servers can face a runtime error (e.g. I/O error) at an arbitrary timing. This patch changes the protocol to allow an error packet to be sent instead of any packet. Without this protocol spec change

[PATCH v2 1/2] Use packet_reader instead of packet_read_line

2018-12-29 Thread Masaya Suzuki
By using and sharing a packet_reader while handling a Git pack protocol request, the same reader option is used throughout the code. This makes it easy to set a reader option to the request parsing code. Signed-off-by: Masaya Suzuki --- builtin/archive.c | 19 ++--- builtin/receive-

Re: [PATCH] Use packet_reader instead of packet_read_line

2018-12-29 Thread Masaya Suzuki
Sorry. This is really broken. I'll fix the tests and send another version.

[PATCH v2 2/2] Unset CURLOPT_FAILONERROR

2018-12-29 Thread Masaya Suzuki
When GIT_CURL_VERBOSE is set, libcurl produces request/response headers to stderr. However, if the response is an error response and CURLOPT_FAILONERROR is set, libcurl stops parsing the response, and it won't dump the headers. Showing HTTP response headers is useful for debugging, especially for n

[PATCH v2 1/2] Change how HTTP response body is returned

2018-12-29 Thread Masaya Suzuki
This changes the way HTTP response body is returned in http_request_reauth and post_rpc. 1. http_request_reauth makes up to two requests; one without a credential and one with a credential. The first request can fail if it needs a credential. When the keep_error option is specified, the r

[PATCH v2 0/2] Show HTTP headers of failed requests with GIT_CURL_VERBOSE

2018-12-29 Thread Masaya Suzuki
When GIT_CURL_VERBOSE is set, libcurl produces request/response headers to stderr. However, if the response is an error response and CURLOPT_FAILONERROR is set, libcurl stops parsing the response, and it won't dump the headers. Showing HTTP response headers is useful for debugging, especially for n

Re: [PATCH/RFC v1 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2018-12-29 Thread Philip Oakley
(adding Brian as cc who was in the original thread) On 29/12/2018 15:48, Adrián Gimeno Balaguer wrote: Hello again. I appreciate the grown interest in this issue. Torsten, may I know what is the benefit on your code? My PR solved it by only tweaking the utf8.c's function 'has_prohibited_utf_bo

[PATCH v4 11/16] sequencer: refactor skip_unnecessary_picks() to work on a todo_list

2018-12-29 Thread Alban Gruin
This refactors skip_unnecessary_picks() to work on a todo_list. As this function is only called by complete_action() (and thus is not used by rebase -p), the file-handling logic is completely dropped here. Instead of truncating the todo list’s buffer, the items are moved to the beginning of the l

[PATCH v4 16/16] rebase--interactive: move transform_todo_file() to rebase--interactive.c

2018-12-29 Thread Alban Gruin
As transform_todo_file() is only needed inside of rebase--interactive.c, it is moved there from sequencer.c. Signed-off-by: Alban Gruin --- builtin/rebase--interactive.c | 26 +- sequencer.c | 23 --- sequencer.h |

[PATCH v4 14/16] rebase-interactive: rewrite edit_todo_list() to handle the initial edit

2018-12-29 Thread Alban Gruin
edit_todo_list() is changed to work on a todo_list, and to handle the initial edition of the todo list (ie. making a backup of the todo list). It does not check for dropped commits yet, as todo_list_check() does not take the commits that have already been processed by the rebase (ie. the todo list

[PATCH v4 15/16] sequencer: use edit_todo_list() in complete_action()

2018-12-29 Thread Alban Gruin
This changes complete_action() to use edit_todo_list(), now that it can handle the initial edit of the todo list. Signed-off-by: Alban Gruin --- Changes due to conflicts with nd/the-index. sequencer.c | 21 +++-- 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/seq

[PATCH v4 03/16] sequencer: remove the 'arg' field from todo_item

2018-12-29 Thread Alban Gruin
The 'arg' field of todo_item used to store the address of the first byte of the parameter of a command in a todo list. It was associated with the length of the parameter (the 'arg_len' field). This replaces the 'arg' field by 'arg_offset'. This new field does not store the address of the paramet

[PATCH v4 04/16] sequencer: refactor transform_todos() to work on a todo_list

2018-12-29 Thread Alban Gruin
This refactors transform_todos() to work on a todo_list. The function is renamed todo_list_transform(). As rebase -p still need to check the todo list from the disk, a new function is introduced, transform_todo_file(). It is still used by complete_action() and edit_todo_list() for now, but they

[PATCH v4 12/16] rebase-interactive: use todo_list_write_to_file() in edit_todo_list()

2018-12-29 Thread Alban Gruin
Just like complete_action(), edit_todo_list() used a function (transform_todo_file()) that read the todo list from the disk and wrote it back, resulting in useless disk accesses. This changes edit_todo_list() to call directly todo_list_write_to_file() instead. Signed-off-by: Alban Gruin --- Chan

[PATCH v4 05/16] sequencer: introduce todo_list_write_to_file()

2018-12-29 Thread Alban Gruin
This introduces a new function to recreate the text of a todo list from its commands and write it to a file. This will be useful as the next few commits will change the use of the buffer in struct todo_list so it will no longer be a mirror of the file on disk. This functionality already exists in

[PATCH v4 10/16] sequencer: change complete_action() to use the refactored functions

2018-12-29 Thread Alban Gruin
complete_action() used functions that read the todo-list file, made some changes to it, and wrote it back to the disk. The previous commits were dedicated to separate the part that deals with the file from the actual logic of these functions. Now that this is done, we can call directly the "logic

[PATCH v4 13/16] rebase-interactive: append_todo_help() changes

2018-12-29 Thread Alban Gruin
This moves the writing of the comment "Rebase $shortrevisions onto $shortonto ($command_count commands)" from todo_list_write_to_file() to append_todo_help(). shortrevisions, shortonto, and command_count are passed as parameters to append_todo_help(). During the initial edit of the todo list, sho

[PATCH v4 09/16] sequencer: make sequencer_make_script() write its script to a strbuf

2018-12-29 Thread Alban Gruin
This makes sequencer_make_script() write its script to a strbuf (ie. the buffer of a todo_list) instead of a FILE. This reduce the amount of read/write made by rebase interactive. Signed-off-by: Alban Gruin --- Changes due to conflicts with nd/the-index. builtin/rebase--interactive.c | 13

[PATCH v4 08/16] sequencer: refactor rearrange_squash() to work on a todo_list

2018-12-29 Thread Alban Gruin
This refactors rearrange_squash() to work on a todo_list to avoid redundant reads and writes. The function is renamed todo_list_rearrange_squash(). The old version created a new buffer, which was directly written to the disk. This new version creates a new item list by just copying items from th

[PATCH v4 02/16] sequencer: make the todo_list structure public

2018-12-29 Thread Alban Gruin
This makes the structures todo_list and todo_item, and the functions todo_list_release() and parse_insn_buffer(), accessible outside of sequencer.c. Signed-off-by: Alban Gruin --- Some changes were introduced because of the conflict resolution with nd/the-index. They mostly consist of adding a p

[PATCH v4 07/16] sequencer: refactor sequencer_add_exec_commands() to work on a todo_list

2018-12-29 Thread Alban Gruin
This refactors sequencer_add_exec_commands() to work on a todo_list to avoid redundant reads and writes to the disk. Instead of inserting the `exec' commands between the other commands and re-parsing the buffer at the end, they are appended to the buffer once, and a new list of items is created.

[PATCH v4 00/16] sequencer: refactor functions working on a todo_list

2018-12-29 Thread Alban Gruin
At the center of the "interactive" part of the interactive rebase lies the todo list. When the user starts an interactive rebase, a todo list is generated, presented to the user (who then edits it using a text editor), read back, and then is checked and processed before the actual rebase takes pla

[PATCH v4 06/16] sequencer: refactor check_todo_list() to work on a todo_list

2018-12-29 Thread Alban Gruin
This refactors check_todo_list() to work on a todo_list to avoid redundant reads and writes to the disk. The function is renamed todo_list_check(). The parsing of the two todo lists is left to the caller. As rebase -p still need to check the todo list from the disk, a new function is introduced,

[PATCH v4 01/16] sequencer: changes in parse_insn_buffer()

2018-12-29 Thread Alban Gruin
This clears the number of items of a todo_list before parsing it to allow to parse the same list multiple times without issues. As its items are not dynamically allocated, or don’t need to allocate memory, no additionnal memory management is required here. Furthermore, if a line is invalid, the t

Re: [PATCH/RFC v1 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2018-12-29 Thread Adrián Gimeno Balaguer
Hello again. I appreciate the grown interest in this issue. Torsten, may I know what is the benefit on your code? My PR solved it by only tweaking the utf8.c's function 'has_prohibited_utf_bom', which is likely the shortest way: https://github.com/git/git/pull/550/files In order to make sure ev

IRIS Expands Partnership & Services of Biometric Secure Products & Solutions

2018-12-29 Thread Khaled Ahmed
Greetings from IRIS Corporation Berhad (“IRIS”) It gives us great pleasure to introduce IRIS, a global technology solution provider with legal and beneficial ownerships of systems and technologies relating to smartcard based applications and solutions such as, but not limited to, national eID ca

Re: What's cooking in git.git (Dec 2018, #02; Fri, 28)

2018-12-29 Thread Denton Liu
On Fri, Dec 28, 2018 at 10:04:13AM -0800, Junio C Hamano wrote: > * dl/remote-save-to-push (2018-12-11) 1 commit > - remote: add --save-to-push option to git remote set-url > > "git remote set-url" learned a new option that moves existing value > of the URL field to pushURL field of the remote

[PATCH/RFC v1 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2018-12-29 Thread tboegi
From: Torsten Bögershausen Users who want UTF-16 files in the working tree set the .gitattributes like this: test.txt working-tree-encoding=UTF-16 After a checkout, the resulting file has a BOM and is encoded in "UTF-16". The unicode standard allows both little- and big-endianess (LE/BE) for tho

Hello Dear,,

2018-12-29 Thread Janet Nixon
My dear kindly talk to me i am still waiting why you did not respond to my previous mail?.

Re: RFE: version-controlled merge rules

2018-12-29 Thread hpa
On December 28, 2018 6:35:23 AM PST, Junio C Hamano wrote: >Jonathan Nieder writes: > >> The main issue I see is that this would make it a little *too* easy >to >> run arbitrary code on the user's machine. Build systems often >already >> lead to that, but users are more familiar with the risks f

Re: [PATCH v2 0/4] Allow 'cherry-pick -m 1' for non-merge commits

2018-12-29 Thread Sergey Organov
Junio C Hamano writes: > Sergey Organov , Sergey Organov > writes: > >> Hi Junio, >> >> What's the status of these patches? > > The status of these patches is "Just updated on the list", as far as > I am concerned, and its cover letter would have described what's > improved relative to the previ