By default, git-diff shows changes and pathnames relative to the
repository root. Setting the diff.relative config option to true shows
pathnames relative to the current directory and excludes changes outside
this directory (identical to git diff --relative).
Signed-off-by: Brandon Phillips
Hi,
Steps to reproduce:
$ git --version
git version 1.9.1
$ wc -l /tmp/1
9090 /tmp/1
$ head /tmp/1
delete refs/pull/1/head
create refs/heads/pull/1 86b715f346e52920ca7c9dfe65424eb9946ebd61
delete refs/pull/1/merge
create refs/merges/1 c0633abdc5311354c9729374e0ba25c97a89f69e
...
$ ulimit -n
1024
On Dec 18, 2014, at 2:18 PM, Junio C Hamano gits...@pobox.com wrote:
Kenneth Lorber k...@his.com writes:
Bug: exit codes from (at least) internal commands are handled incorrectly.
E.g. git-merge-file, docs say:
The exit value of this program is negative on error, and the number of
From: kel...@shysecurity.com
By default, git-diff shows changes and pathnames relative to the
repository root. Setting the diff.relative config option to true
shows pathnames relative to the current directory and excludes changes
outside this directory (identical to git diff --relative).
On Thu, Dec 11, 2014 at 11:26:47AM -0800, Junio C Hamano wrote:
The right approach would be more like allocating one more bit in
struct rev_info (call that edge_hint_aggressive), give a new option
--objects-edge-aggressive, and do something like
if (thin) {
On Fri, Dec 19, 2014 at 11:30 AM, Michael J Gruber
g...@drmicha.warpmail.net wrote:
Anastas Dancha schrieb am 19.12.2014 um 16:44:
Hello Johannes,
On Fri, Dec 19, 2014 at 4:37 AM, Johannes Schindelin
johannes.schinde...@gmx.de wrote:
[...]
There is one bit left to clarify: let me guess, you
On Thu, Dec 11, 2014 at 05:51:54PM +0700, Duy Nguyen wrote:
I'm glad it's now working better for you. Out of curiosity, have you
enabled pack bitmap on this repo? I would expect it to reduce time
some (or a lot) more, or we would find something to optimize further.
The client performs much,
In commit fbd4a70 (list-objects: mark more commits as edges in
mark_edges_uninteresting - 2013-08-16), we marked an increasing number
of edges uninteresting. This change, and the subsequent change to make
this conditional on --objects-edge, are used by --thin to make much
smaller packs for
This series contains patches to address a significant push performance
regression in repositories with large amounts of refs. It avoids
performing expensive edge marking unless the repository is shallow.
The first patch in the series is a fix for a minor typo I discovered
when editing the
Using --objects-edge-aggressive is important for shallow repos, as it
can result in a much smaller pack (in some cases, 10% of the size).
However, it performs poorly on large non-shallow repositories with many
refs. Since shallow repositories are less likely to have many refs (due
to having less
Add the missing article a.
Signed-off-by: brian m. carlson sand...@crustytoothpaste.net
---
Documentation/rev-list-options.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/rev-list-options.txt
b/Documentation/rev-list-options.txt
index afccfdc..2277fcb
11 matches
Mail list logo
