Sun Chao (my former colleague at Huawei) found a bug of
git-pack-redundant. If there are too many packs and many of them overlap
each other, running `git pack-redundant --all` will exhaust all memories
and the process will be killed by kernel.
There is a script in commit log of commit 2/3, which
From: Jiang Xin
Add test cases for git pack-redundant to validate new algorithm for git
pack-redundant.
Signed-off-by: Jiang Xin
---
t/t5323-pack-redundant.sh | 84 +++
1 file changed, 84 insertions(+)
create mode 100755 t/t5323-pack-redundant.sh
d
From: Sun Chao
When calling `git pack-redundant --all`, if there are too many local
packs and too many redundant objects within them, the too deep iteration
of `get_permutations` will exhaust all the resources, and the process of
`git pack-redundant` will be killed.
The following script could cr
From: Sun Chao
Remove unused functions to find `min` packs, such as `get_permutations`,
`pll_free`, etc.
Signed-off-by: Sun Chao
Signed-off-by: Jiang Xin
---
builtin/pack-redundant.c | 72
1 file changed, 72 deletions(-)
diff --git a/builtin/p
Am 02.01.19 um 00:19 schrieb SZEDER Gábor:
Alas, it has been reported that NetBSD's /bin/sh does complain about
them:
./test-lib.sh: 327: Syntax error: Bad substitution
where line 327 contains the first ${BASH_VERSINFO[0]} array access.
diff --git a/t/test-lib.sh b/t/test-lib.sh
index 0f1
Hello & Happy New Year!
I've recently switched from openSUSE 42.3 (perl 5.18.2 & git 2.13.7) to
the openSUSE Tumbleweed (perl 5.28.1 & git 2.20.1) and send-email
doesn't work for me anymore.
FWIW it doesn't seem like a git regression. I've manually installed
2.13.7 in my new OS and it also fails
One of our test scripts, 't1510-repo-setup.sh' [1], still can't be
reliably run with '-x' tracing enabled, unless it's executed with a
Bash version supporting BASH_XTRACEFD (since v4.1). We have a lengthy
condition to check the version of the shell running the test script,
and disable tracing if i
Here's a simple regression test -- haven't had time to bisect this
```
#!/usr/bin/env bash
set -euxo pipefail
rm -rf src dest
git --version
git init src
echo hi > src/a
git -C src add .
git -C src commit -m "initial commit"
rev="$(git -C src rev-parse HEAD)"
git clone --no-checkout src dest
gi
Remove TODO that was left in from:
commit 110240588d (Merge branch 'sb/object-store-alloc' - 2018-06-25)
Todo can be removed as:
9d2c97016f (commit.h: delete 'util' field in struct commit - 2018-05-19)
deletes commit->util.
Signed-off-by: Albert Burt
---
Thanks for looking at this for me Duy. I
I found more issues with completion for git show ref:path, so here I add one
more patch.
Chayoung You (2):
zsh: complete unquoted paths with spaces correctly
completion: treat results of git ls-tree as file paths
contrib/completion/git-completion.bash | 35 +++---
contrib
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
Let's say there are files named 'foo bar.txt', and 'abc def/test.txt' in
repository. When following commands trigger a completion:
git show HEAD:fo
git show HEAD:ab
The completion results in bash/zsh:
git show HEAD:foo bar.txt
git show HEAD:abc def/
Where the both of them have a
On Mon, Dec 31, 2018 at 01:31:21PM +0100, Marc Balmer wrote:
>
>
> > Am 31.12.2018 um 12:36 schrieb Duy Nguyen :
> >
> > On Mon, Dec 31, 2018 at 6:24 PM Marc Balmer wrote:
> >> In a (private) Email to me, he indicated that had no time for a fix.
> >> Maybe he can speak up here?
> >
> > Well,
On Tue, Jan 1, 2019 at 7:02 AM Albert Burt wrote:
>
> The code that was merged with commit 1102405 left in an TODO that
People usually use something this to produce the commit reference
git show -s --date=short --pretty='format:%h (%s - %ad)'
which produces
110240588d (Merge branch 'sb/obj
14 matches
Mail list logo
