Re: [PATCH v3] l10n: localizable upload progress messages

On 2019-06-22 at 21:42:33, Johannes Sixt wrote: > Am 22.06.19 um 11:36 schrieb Dimitriy Ryazantcev: > > diff --git a/strbuf.c b/strbuf.c > > index 0e18b259ce..0a3ebc3749 100644 > > --- a/strbuf.c > > +++ b/strbuf.c > > @@ -814,20 +814,28 @@ void strbuf_addstr_urlencode(struct strbuf *sb, const > >

Re: [PATCH v3] l10n: localizable upload progress messages

Am 22.06.19 um 11:36 schrieb Dimitriy Ryazantcev: > Signed-off-by: Dimitriy Ryazantcev > --- > progress.c | 4 +++- > strbuf.c | 16 > 2 files changed, 15 insertions(+), 5 deletions(-) > > diff --git a/progress.c b/progress.c > index a2e8cf64a8..61d8cf5d04 100644 > --- a/prog

[GSoC] Blogging with Rohit

Hi Everyone! Last week was not so productive so, this post is a bit shorter. Thanks Rohit [1]: https://rashiwal.me/2019/unproductive-week/

[PATCH] doc: don't use git.kernel.org as example gitweb URL

git.kernel.org uses cgit, not gitweb, these days: $ w3m -dump 'http://git.kernel.org/?p=git/git.git;a=tree;f=gitweb' | grep -w generated generated by cgit 1.2-0.3.lf.el7 (git 2.18.0) at 2019-06-22 16:14:38 + Signed-off-by: Jakub Wilk --- Documentation/gitweb.txt | 3 +-- 1 file cha

Re: [PATCH v3] l10n: localizable upload progress messages

Duy Nguyen wrote: > > On Sat, Jun 22, 2019 at 4:37 PM Dimitriy Ryazantcev > wrote: > > diff --git a/strbuf.c b/strbuf.c > > index 0e18b259ce..0a3ebc3749 100644 > > --- a/strbuf.c > > +++ b/strbuf.c > > @@ -814,20 +814,28 @@ void strbuf_addstr_urlencode(struct strbuf *sb, const > > char *s, > >

Re: [PATCH 01/14] completion: zsh: fix __gitcomp_direct()

On Fri, Jun 21, 2019 at 5:31 PM Felipe Contreras wrote: > > Many callers append a space suffix, but zsh automatically appends a > space, making the completion add two spaces, for example: > --- a/contrib/completion/git-completion.zsh > +++ b/contrib/completion/git-completion.zsh > @@ -73,7 +73,7

[PATCH] rm: add --intent-to-add, to be used with --cached

An index entry serves two purposes: to keep the content to be committed, and to mark that the same path on worktree is tracked. When git rm --cached foo is called and there is "foo" in worktree, its status is changed from tracked to untracked. Which I think is not intended, at least from the

Re: [PATCH v3] l10n: localizable upload progress messages

On Sat, Jun 22, 2019 at 4:37 PM Dimitriy Ryazantcev wrote: > diff --git a/strbuf.c b/strbuf.c > index 0e18b259ce..0a3ebc3749 100644 > --- a/strbuf.c > +++ b/strbuf.c > @@ -814,20 +814,28 @@ void strbuf_addstr_urlencode(struct strbuf *sb, const > char *s, > void strbuf_humanise_bytes(struct strbu

Re: windows: error cannot lock ref ... unable to create lock

On 18/06/2019 18:01, Eric Sunshine wrote: On Tue, Jun 18, 2019 at 12:39 PM Anthony Sottile wrote: + git fetch origin --tags Unpacking objects: 100% (10/10), done. From https://github.com/asottile-archive/git-windows-branch-test * [new branch] master -> origin/master error: cannot lo

Re: [PATCH v2 1/1] submodule foreach: fix recursion of options

Johannes Schindelin wrote: Hello Johannes, thank your for the review. Sorry for the spam, I messed up with the replytoall command. > Hi Morian, > > On Tue, 18 Jun 2019, Morian Sonnet wrote: > > > "Morian Sonnet via GitGitGadget" wrote: > > > > > Calling > > > > > > git submodule foreach --

[PATCH v2 3/3] config: simplify parsing of unit factors

Just return the value of the factor or zero for unrecognized strings instead of using an output reference and a separate return value to indicate success. This is shorter and simpler. It basically reverts that function to before c8deb5a146 ("Improve error messages when int/long cannot be parsed f

[PATCH v2 2/3] config: don't multiply in parse_unit_factor()

parse_unit_factor() multiplies the number that is passed to it with the value of a recognized unit factor (K, M or G for 2^10, 2^20 and 2^30, respectively). All callers pass in 1 as a number, though, which allows them to check the actual multiplication for overflow before they are doing it themsel

Re: [PATCH 4/4] config: avoid calling `labs()` on too-large data type

Am 21.06.19 um 20:35 schrieb Johannes Schindelin: > Hi René, > > On Thu, 20 Jun 2019, René Scharfe wrote: > >> Subject: [PATCH] config: simplify unit suffix handling >> >> parse_unit_factor() checks if a K, M or G is present after a number and >> multiplies it by 2^10, 2^20 or 2^30, respectively.

[PATCH v2 1/3] config: use unsigned_mult_overflows to check for overflows

parse_unit_factor() checks if a K, M or G is present after a number and multiplies it by 2^10, 2^20 or 2^30, respectively. One of its callers checks if the result is smaller than the number alone to detect overflows. The other one passes 1 as the number and does multiplication and overflow check

Re: What's cooking in git.git (Jun 2019, #05; Wed, 19)

20.06.2019, 00:35, "Junio C Hamano" : > * am/p4-branches-excludes (2019-04-02) 8 commits >  - git-p4: respect excluded paths when detecting branches >  - git-p4: add failing test for "git-p4: respect excluded paths when > detecting branches" >  - git-p4: don't exclude other files with same prefix

[PATCH v3] l10n: localizable upload progress messages

Signed-off-by: Dimitriy Ryazantcev --- progress.c | 4 +++- strbuf.c | 16 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/progress.c b/progress.c index a2e8cf64a8..61d8cf5d04 100644 --- a/progress.c +++ b/progress.c @@ -151,7 +151,9 @@ static void throughput_s

[PATCH v2] l10n: localizable upload progress messages

Signed-off-by: Dimitriy Ryazantcev --- progress.c | 4 +++- strbuf.c | 16 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/progress.c b/progress.c index a2e8cf64a8..61d8cf5d04 100644 --- a/progress.c +++ b/progress.c @@ -151,7 +151,9 @@ static void throughput_s

A partir de Sra, Serena Buafoh.

-- Meu querido, Eu quero financiar um projeto de caridade em seu país para o benefício dos menos privilegiados, Por favor, confirme seu interesse se você puder lidar com tal projeto com honestidade. Eu vou te dar mais detalhes depois de receber sua resposta, Deus te abençoê, Saudações, Sra, Sere