Assalamu`Alaikum.

Greetings from Dr. mohammad ouattara. Assalamu`Alaikum. My Name is Dr. mohammad ouattara, I am a banker by profession. I'm from Ouagadougou, Burkina Faso, West Africa. My reason for contacting you is to transfer an abandoned $14.6M to your account. The owner of this fund died since 2004

Re: [PATCH v2 03/18] ref-filter: make valid_atom as function parameter

2018-01-18 9:20 GMT+03:00 Оля Тележная : > 2018-01-18 1:39 GMT+03:00 Christian Couder : >> On Wed, Jan 17, 2018 at 10:43 PM, Jeff King wrote: >>> On Tue, Jan 16, 2018 at 09:55:22AM +0300, Оля Тележная wrote: >>> > IOW, the

[PATCH 03/11] fetch tests: add a tag to be deleted to the pruning tests

Add a tag to be deleted to the fetch --prune tests. The tag is always kept for now, which is the expected behavior, but now I can add a test for tag pruning in a later commit. Signed-off-by: Ævar Arnfjörð Bjarmason --- t/t5510-fetch.sh | 93

Re: [PATCH v2] diff: add --compact-summary option to complement --stat

On Fri, Jan 19, 2018 at 4:23 AM, Ævar Arnfjörð Bjarmason wrote: > Wait, isn't there a bug here in the existing --summary code, its > documentation says it'll show information "such as creations, renames > and mode changes". > > But even though your --compact-summary shows that

[PATCH v2 2/2] http: support omitting data from traces

GIT_TRACE_CURL provides a way to debug what is being sent and received over HTTP, with automatic redaction of sensitive information. But it also logs data transmissions, which significantly increases the log file size, sometimes unnecessarily. Add an option "GIT_TRACE_CURL_NO_DATA" to allow the

[PATCH v2 1/2] http: support cookie redaction when tracing

When using GIT_TRACE_CURL, Git already redacts the "Authorization:" and "Proxy-Authorization:" HTTP headers. Extend this redaction to a user-specified list of cookies, specified through the "GIT_REDACT_COOKIES" environment variable. Signed-off-by: Jonathan Tan ---

Re: [PATCH 06/11] git fetch doc: add a new section to explain the ins & outs of pruning

On Thu, Jan 18, 2018 at 7:00 PM, Ævar Arnfjörð Bjarmason wrote: > Add a new section to canonically explain how remote reference pruning > works, and how users should be careful about using it in conjunction > with tag refspecs in particular. > > A subsequent commit will update

RE: [RFC PATCH] NonStop port changes for git 2.16.0.

On January 18, 2018 7:11 PM, Ævar Arnfjörð Bjarmason wrote: > On Thu, Jan 18 2018, Stefan Beller jotted: > > On Thu, Jan 18, 2018 at 2:42 PM, wrote: > >> Further: there are 6 known breakages that have been reported. The > >> perl issues relating to completion codes

[RFC/PATCH 11/11] WIP fetch: add a --fetch-prune option and fetch.pruneTags config

[WIP: This doesn't (yet) work as advertised, see further WIP note below] Add a --fetch-prune option to git-fetch along with fetch.pruneTags config option. This allows for doing: git fetch origin -p -P Or simply: git config fetch.prune true && git config fetch.pruneTags true &&

[PATCH 00/11] document & test fetch pruning + WIP fetch.pruneTags

Michael Giuffrida noted that the git-remote docs were very confusing, and upthread I said I wanted this shiny related thing in 11/11. Along the way I fixed up fetch tests & documentation to hopefully be a lot less confusing. I think 1-10/11 of this makes sense for inclusion as-is (pending review

[PATCH 01/11] fetch tests: refactor in preparation for testing tag pruning

In a subsequent commit this function will learn to test for tag pruning, prepare for that by making space for more variables, and making it clear that "expected" here refers to branches. Signed-off-by: Ævar Arnfjörð Bjarmason --- t/t5510-fetch.sh | 9 ++--- 1 file changed,

[PATCH 08/11] git-fetch & config doc: link to the new PRUNING section

Amend the documentation for fetch.prune, fetch..prune and --prune to link to the recently added PRUNING section. I'd have liked to link directly to it with "<>" from fetch-options.txt, since it's included in git-fetch.txt (git-pull.txt also includes it, but doesn't include that option). However

Re: [PATCH v2] diff: add --compact-summary option to complement --stat

On Fri, Jan 19, 2018 at 1:57 AM, Eric Sunshine wrote: >> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt >> @@ -188,6 +188,17 @@ and accumulating child directory counts in the parent >> directories: >> +--compact-summary:: >> + Output a

[PATCH 02/11] fetch tests: arrange arguments for future readability

Re-arrange the arguments to the test_configured_prune() function used in this test to pass the arguments to --fetch last. A subsequent change will test for more elaborate fetch arguments, including long refspecs. It'll be more readable to be able to wrap those on a new line of their own.

[PATCH 06/11] git fetch doc: add a new section to explain the ins & outs of pruning

Add a new section to canonically explain how remote reference pruning works, and how users should be careful about using it in conjunction with tag refspecs in particular. A subsequent commit will update the git-remote documentation to refer to this section, and details the motivation for writing

[PATCH 07/11] git remote doc: correct dangerous lies about what prune does

The "git remote prune " command uses the same machinery as "git fetch --prune", and shares all the same caveats, but its documentation has suggested that it'll just "delete stale remote-tracking branches under ". This isn't true, and hasn't been true since at least v1.8.5.6 (the oldest version I

[PATCH 05/11] fetch tests: test --prune and refspec interaction

Add a test for the interaction between explicitly provided refspecs and fetch.prune. There's no point in adding this boilerplate to every combination of unset/false/true, it's instructive and sufficient to show that no matter if the variable is unset, false or true the refspec on the command-line

[PATCH 09/11] fetch: don't redundantly null something calloc() gave us

Stop redundantly NULL-ing the last element of the refs structure, which was retrieved via calloc() and is thus guaranteed to be pre-NULL'd. This code dates back to b888d61c83 ("Make fetch a builtin", 2007-09-10), where wasn't any reason to do this back then either, it's just something left over

[PATCH 04/11] fetch tests: double quote a variable for interpolation

If the $cmdline variable contains multiple arguments they won't be interpolated correctly since the body of the test is single quoted. I don't know what part of test-lib.sh is expanding variables within single-quoted strings, but interpolating this inline is the desired behavior here. This will

[PATCH 10/11] fetch tests: add scaffolding for the new fetch.pruneTags

The fetch.pruneTags configuration doesn't exist yet, but will be added in a subsequent commit. Since testing for it requires adding new parameters to the test_configured_prune function it's easier to review this patch first to assert that no functional changes are introduced yet. Signed-off-by:

[ANNOUNCE] Git Merge Contributor's Summit Mar 7, 2018, Barcelona

Git Merge 2018 is happening on March 8th; there will be a Contributor's Summit the day before. Here are the details: When: Wednesday, March 7, 2018. 10am-5pm. Where: Convent Dels Àngels[1], Barcelona, Spain What: Round-table discussion about Git Who: All contributors to Git or related

Re: [RFC PATCH] NonStop port changes for git 2.16.0.

On Thu, Jan 18 2018, Stefan Beller jotted: > On Thu, Jan 18, 2018 at 2:42 PM, wrote: >> Further: there are 6 known breakages that have been reported. The perl >> issues relating to completion codes are being examined at present by the >> platform support teams so

Re: git 2.16.0 segfaults on clone of specific repo

[+cc:brian] On Thu, Jan 18, 2018 at 3:55 PM, Александр Булаев wrote: > I found that git 2.16.0 segfaults on clone of vim-colorschemes repo. > > (lldb) run > Process 25643 launched: '/usr/local/bin/git' (x86_64) > Cloning into 'vim-colorschemes'... > remote: Counting

Re: [PATCH v2] diff: add --compact-summary option to complement --stat

On Fri, Jan 19, 2018 at 5:48 AM, Jeff King wrote: > On Thu, Jan 18, 2018 at 05:05:46PM +0700, Nguyễn Thái Ngọc Duy wrote: > >> This is partly inspired by gerrit web interface which shows diffstat >> like this, e.g. with commit 0433d533f1 (notice the "A" column on the >> third

[PATCH v2 0/2] Cookie redaction during GIT_TRACE_CURL

Thanks, Eric. Changes in v2: - documented all environment variables introduced - made test more clear by ensuring that no cookie keys are suffixes or prefixes of others - tested empty value As far as I can tell, it does not seem possible that Git generates a cookie with no equals sign (like

Re: [PATCH 3/3] read-cache: don't write index twice if we can't write shared index

On Fri, Jan 19, 2018 at 5:32 AM, SZEDER Gábor wrote: > On Thu, Jan 18, 2018 at 10:37 PM, Jeff King wrote: >> On Thu, Jan 18, 2018 at 10:00:14PM +0700, Duy Nguyen wrote: >> >>> The test suite was run as root, no wonder why my removing write access >>> has no

Re: [PATCH v3 1/3] read-cache: fix reading the shared index for other repos

On Thu, Jan 18, 2018 at 1:16 AM, Jonathan Nieder wrote: > Hi, > > Duy Nguyen wrote: >> On Wed, Jan 17, 2018 at 4:42 AM, Brandon Williams wrote: > >>> IIUC Split index is an index extension >>> that can be enabled to limit

Re: [PATCH v2 2/2] send-email: Support separate Reply-To address

On 17 January 2018 at 19:08, Christian Ludwig wrote: > In some projects contributions from groups are only accepted from a > common group email address. But every individual may want to recieve > replies to her own personal address. That's what we have 'Reply-To' >

[PATCH v3 2/2] sha1_file: improve sha1_file_name() perfs

As sha1_file_name() could be performance sensitive, let's make it faster by using strbuf_addstr() and strbuf_addc() instead of strbuf_addf(). Helped-by: Derrick Stolee Helped-by: Jeff Hostetler Signed-off-by: Christian Couder

[PATCH v3 1/2] sha1_file: remove static strbuf from sha1_file_name()

Using a static buffer in sha1_file_name() is error prone and the performance improvements it gives are not needed in many of the callers. So let's get rid of this static buffer and, if necessary or helpful, let's use one in the caller. Suggested-by: Jeff Hostetler

Re:

I have charity donation of £7 Million British Pound to give you and i hope you will be sincere to use this money for charity work according to my will, to help orphans, widows and less privileged ones. My name is Mrs. Emile Kenold from London, I have been suffering from lung cancer which had

[PATCH v2] packfile: use get_be64() for large offsets

The pack-index version 2 format uses two 4-byte integers in network- byte order to represent one 8-byte value. The current implementation has several code clones for stitching these integers together. Use get_be64() to create an 8-byte integer from two 4-byte integers represented this way.

<    1   2