Re: [PATCH v10 1/3] parse-options.c: make OPTION__COUNTUP understand "unspecified" values

On Sun, Mar 27, 2016 at 8:15 AM, Eric Sunshine wrote: > On Sat, Mar 26, 2016 at 3:48 PM, Pranit Bauva wrote: >> parse-options.c: make OPTION__COUNTUP understand "unspecified" values > > A bit clearer: s/understand/respect/ > Also: s/__/_/ Sure. >> The reason to make it understand negative value

Re: [PATCH 00/21] replacement for dt/refs-backend-lmdb v7 patch 04/33

On 03/24/2016 07:47 AM, David Turner wrote: > [...] > I incorporated your changes into the lmdb backend. To make merging > later more convenient, I rebased on top of pu -- I think this mainly > depends on jk/check-repository-format, but I also included some fixes > for a couple of tests that had b

Re: [PATCH v10 3/3] commit: add a commit.verbose config variable

On Sat, Mar 26, 2016 at 3:48 PM, Pranit Bauva wrote: > Add commit.verbose configuration variable as a convenience for those > who always prefer --verbose taking care of multiple levels of verbosity. What does "taking care of multiple levels of verbosity" mean? I suppose you mean that commit.verbo

Re: [PATCH v10 2/3] t7507-commit-verbose: store output of grep in a file

On Sat, Mar 26, 2016 at 3:48 PM, Pranit Bauva wrote: > So that we can see how many diffs were contained in the message and use > them in individual tests where ever it is required. Also use > write_script() to create the fake "editor". It is important to explain *why* you want to be able to count

Re: [PATCH v10 1/3] parse-options.c: make OPTION__COUNTUP understand "unspecified" values

On Sat, Mar 26, 2016 at 3:48 PM, Pranit Bauva wrote: > parse-options.c: make OPTION__COUNTUP understand "unspecified" values A bit clearer: s/understand/respect/ Also: s/__/_/ > The reason to make it understand negative values or more specifically > "unspecified" values is to give the ability to

穿刺拖曳

你的老朋友邀你来Q群:343257759

[PATCH v10 2/3] t7507-commit-verbose: store output of grep in a file

So that we can see how many diffs were contained in the message and use them in individual tests where ever it is required. Also use write_script() to create the fake "editor". Helped-by: Eric Sunshine Signed-off-by: Pranit Bauva --- t/t7507-commit-verbose.sh | 17 +++-- 1 file chan

[PATCH v10 1/3] parse-options.c: make OPTION__COUNTUP understand "unspecified" values

The reason to make it understand negative values or more specifically "unspecified" values is to give the ability to differentiate whether `--option` or `--no-option` was specified at all. Many uses of COUNTUP have now been replaced with BOOL and what remains are verbose/quiet/force. This change w

[PATCH v10 3/3] commit: add a commit.verbose config variable

Add commit.verbose configuration variable as a convenience for those who always prefer --verbose taking care of multiple levels of verbosity. Helped-by: Junio C Hamano Helped-by: Eric Sunshine Signed-off-by: Pranit Bauva --- The previous version of the patch are: - [v9] $gmane/288820 - [v8]

[PATCH v3] t7012: Implement test for git-checkout

Previously a TODO; add a test for git-checkout skipping a file with the skip-worktree bit set. Signed-off-by: Chhatoi Pritam Baral --- Replaced test_must_fail around grep with '!', as suggested by Eric. t/t7012-skip-worktree-writing.sh | 12 +++- 1 file changed, 11 insertions(+), 1 del

Re: [RFC/GSOC] Git Beginner | Warnings for potentially destructive commands

Jacob Keller writes: > If possible, I would suggest aiming for generating the actual topology > that the user is seeing, customized so that it gives relevenat > information, rather than static examples. Using the real topology in a useful way is actually pretty hard. It's quite easy to throw the

Re: [Outreachy] Git remote whitelist/blacklist

Hi everyone, I think I will submit the application as it is now, but still it would be great to get feedback on it, as I don't think there was no reply because everything was perfect :( Thank you! And have an awesome weekend. On Thu, Mar 24, 2016 at 5:50 PM, elena petrashen wrote: > Hi, > > I'm

GIT v(+) database versioning question

Hello, may I ask a question: what would be the best way to achieve this with GIT: Database versioning scripts shall be (1) numbered (due to DBmaintain) and (2) incremental. ad 1) When a developer commits a script, I should get the next higher number than the last committed script. E.g. 045

Re: [GSoC] A late proposal: a modern send-email

2016-03-26 17:52 GMT+08:00 惠轶群 : > 2016-03-26 14:18 GMT+08:00 Pranit Bauva : >> On Sat, Mar 26, 2016 at 7:43 AM, 惠轶群 wrote: >>> 2016-03-26 2:16 GMT+08:00 Junio C Hamano : 惠轶群 writes: > # Purpose > The current implementation of send-email is based on perl and has only > a tui

Re: [GSoC] A late proposal: a modern send-email

To make it clearer: 1. there are so many great mail clients, why not let these experts to handle the dispatch of mail? For example, as a One-time-password user of gmail, I have to generate an app password for each terminal device I'd like to send patch on. It's more important that I could no

Re: [GSoC] A late proposal: a modern send-email

2016-03-26 14:18 GMT+08:00 Pranit Bauva : > On Sat, Mar 26, 2016 at 7:43 AM, 惠轶群 wrote: >> 2016-03-26 2:16 GMT+08:00 Junio C Hamano : >>> 惠轶群 writes: >>> # Purpose The current implementation of send-email is based on perl and has only a tui, it has two problems: - user must in

Issue: `git apply` doesn't respect `--work-tree`

[I've quickly looked at the mailing list archive and didn't see this issue reported. However I might be wrong.] The issue is simple: `git apply` does not respect the `--work-tree` argument when called outside the repository. The version of Git I used is OpenSUSE's official 2.1.4 but also 2.7.4