[PATCH v2] l10n: de.po: translate 72 new messages

Translate 72 new messages came from git.pot update in 18a907225 (l10n: git.pot: v2.16.0 round 1 (64 new, 25 removed)) and 005c62fe4 (l10n: git.pot: v2.16.0 round 2 (8 new, 4 removed)). Signed-off-by: Ralf Thielow --- Thanks for the review, Matthias! po/de.po | 227

Hello,

-- Weekend Greetings , I was wondering if you got my previous Email to you regarding my proposal ? best regards

[PATCH v1 1/1] convert_to_git(): safe_crlf/checksafe becomes int conv_flags

From: Torsten Bögershausen When calling convert_to_git(), the checksafe parameter defined what should happen if the EOL conversion (CRLF --> LF --> CRLF) does not roundtrip cleanly. In addition, it also defined if line endings should be renormalized (CRLF --> LF) or kept as they

[PATCH v3 4/3] read-cache: don't try to write index if we can't write shared index

In a0a967568e ("update-index --split-index: do not split if $GIT_DIR is read only", 2014-06-13), we tried to make sure we can still write an index, even if the shared index can not be written. We did so by just calling 'do_write_locked_index()' from 'write_shared_index()'.

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

On 01/08, Thomas Gummerer wrote: > On 01/08, Duy Nguyen wrote: > > On Mon, Jan 8, 2018 at 5:30 AM, Thomas Gummerer > > wrote: > > > @@ -1896,16 +1895,17 @@ int read_index_from(struct index_state *istate, > > > const char *path) > > > split_index->base =

[BUG] test_must_fail: does not correctly detect failures - Was Git 2.16.0-rc2 Test Summary on NonStop

On January 13, 2018 2:31 PM, I wrote: > On January 13, 2018 1:08 PM, I wrote: > > Here’s where things are. This is probably the best git release so far > (ever). > > After applying a4cdf02, I had 6 total breakages. 3 existing, 3 new. > > Many reduced. The test took about 24 hours to run on

Re: GSoC 2018 Org applications. Deadline = January 23, 2018 at 18:00 (CET)

On Mon, Jan 8, 2018 at 12:03 AM, Christian Couder wrote: > On Fri, Jan 5, 2018 at 12:18 PM, Johannes Schindelin > wrote: >> On Fri, 5 Jan 2018, Matthieu Moy wrote: >> >>> If we go for it, we need: >>> >>> * Admins >From the application

RE: Git 2.16.0-rc2 Test Summary on NonStop

On January 13, 2018 1:08 PM, I wrote: > Here’s where things are. This is probably the best git release so far (ever). > After applying a4cdf02, I had 6 total breakages. 3 existing, 3 new. > Many reduced. The test took about 24 hours to run on platform, which is > about 2 hours shorter than 2.13.5.

Re: [PATCH] packed_ref_cache: don't use mmap() for small files

Hi, On Sat, 13 Jan 2018, Kim Gybels wrote: > Take a hint from commit ea68b0ce9f8ce8da3e360aed3cbd6720159ffbee and use Maybe use ea68b0ce9f8 (hash-object: don't use mmap() for small files, 2010-02-21) instead of the full commit name? > read() instead of mmap() for small

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

(one spelling spotted).. From: "Nguyễn Thái Ngọc Duy" 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 line): Documentation/merge-config.txt | 4 + builtin/merge.c

Git for Windows v2.16.0-rc2, was Re: [ANNOUNCE] Git v2.16.0-rc2

Hi team, On Thu, 11 Jan 2018, Junio C Hamano wrote: > A release candidate Git v2.16.0-rc2 is now available for testing > at the usual places. It is comprised of 483 non-merge commits > since v2.15.0, contributed by 80 people, 23 of which are new faces. > > The tarballs are found at: > >

Git 2.16.0-rc2 Test Summary on NonStop

Here’s where things are. This is probably the best git release so far (ever). After applying a4cdf02, I had 6 total breakages. 3 existing, 3 new. Many reduced. The test took about 24 hours to run on platform, which is about 2 hours shorter than 2.13.5. t1308-config-set.sh (2 already discussed and

RE: unused variable in hashmap.h [was: Re: [PATCH] Fixed pervasive enumeration warning in convert.h.]

> Sent: On January 13, 2018 12:13 PM, René Scharfe wrote: > Am 12.01.2018 um 20:52 schrieb Randall S. Becker: > > On a related too many warnings subject, hashmap.h has a variable > > unused (void *item). Is that addressed soon? If not, I can deal with > > it. > Here are the code lines containing

Re: Git uses wrong subkey for signing commits with GPG key

Andrzej Ośmiałowski wrote: > On Sat, Jan 13, 2018 at 1:22 AM, Todd Zullinger wrote: >> I could be wrong, but I think you need to append '!' to >> KEYID to force gpg to use that specific signing subkey. [...] > thanks for reply. You just solved my issue. I will prepare a PR to the

unused variable in hashmap.h [was: Re: [PATCH] Fixed pervasive enumeration warning in convert.h.]

Am 12.01.2018 um 20:52 schrieb Randall S. Becker: > On a related too many warnings subject, hashmap.h has a variable > unused (void *item). Is that addressed soon? If not, I can deal with > it. Here are the code lines containing the variable in question: void *item; while ((item =

Re

-- Hello, I have a project i want to bring to you.. please respond for details Alex

[PATCH] packed_ref_cache: don't use mmap() for small files

Take a hint from commit ea68b0ce9f8ce8da3e360aed3cbd6720159ffbee and use read() instead of mmap() for small packed-refs files. This also fixes the problem[1] where xmmap() returns NULL for zero length[2], for which munmap() later fails. Alternatively, we could simply check for NULL before

RE

I am Mr.Sheng Li Hung, from china I got your information while search for a reliable person, I have a very profitable business proposition for you and i can assure you that you will not regret been part of this mutual beneficial transaction after completion. Kindly get back to me for more details

[PATCH/RFC] diff: add --compact-summary option to complement --stat

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 line): Documentation/merge-config.txt | 4 + builtin/merge.c| 2 + A t/t5573-pull-verify-signatures.sh | 81

Re: Git uses wrong subkey for signing commits with GPG key

Hi Todd, On Sat, Jan 13, 2018 at 1:22 AM, Todd Zullinger wrote: > Hi Andrzej, > > Andrzej Ośmiałowski wrote: >> I have an issue with git and signing commits with GPG subkey. >> >> My setup: >> - master key used for certification only >> - subkey for my main workstation >> -

[PATCH v2] add--interactive: ignore submodule changes except HEAD

For 'add -i' and 'add -p', the only action we can take on a dirty submodule entry is update the index with a new value from its HEAD. The content changes inside (from its own index, untracked files...) do not matter, at least until 'git add -i' learns about launching a new interactive add session

Re: [PATCH] travis-ci: build Git during the 'script' phase

On Sat, Jan 13, 2018 at 05:32:56AM -0500, Jeff King wrote: > According to: > > https://blog.travis-ci.com/2013-05-22-improving-build-visibility-log-folds > > they auto-fold individual commands _except_ the ones in the script > section. Is there a way to manually mark folds in the output? > >

Re: [PATCH] travis-ci: build Git during the 'script' phase

On Fri, Jan 12, 2018 at 02:32:54PM +0100, SZEDER Gábor wrote: > That's the just beginning of a looong list of executed test scripts in > seemingly pseudo-random order. IMHO that's very rarely the interesting > part; I, for one, am only interested in that list in exceptional cases, > e.g. while

Re: git gc --auto yelling at users where a repo legitimately has >6700 loose objects

On Fri, Jan 12, 2018 at 09:23:05PM +0700, Duy Nguyen wrote: > > > Why can't we generate a new cruft-pack on every gc run that > > > detects too many unreachable objects? That would not be as > > > efficient as a single cruft-pack but it should be way more > > > efficient than the individual