Kirill Smelkov k...@navytux.spb.ru writes:
2) alloca(), for small arrays, is used for the same reason - if we change
it to xmalloc()/free() the timings get worse
Do you see any use of it outside compat/?
I thought we specifically avoid alloca() for portability. Also we
do not use
On Fri, Feb 14, 2014 at 09:37:00AM -0800, Junio C Hamano wrote:
Kirill Smelkov k...@mns.spb.ru writes:
Previously diff_tree(), which is now named __diff_tree_sha1(), was
That name with two leading underscores is a rather unfortunate,
especially for a function that is not a file scope
On Thu, Feb 13, 2014 at 11:51:19AM -0800, Junio C Hamano wrote:
Kirill Smelkov k...@mns.spb.ru writes:
+ /* until we go to it next round, .next holds how many bytes we
+* allocated (for faster realloc - we don't need copying old
data).
+*/
+
Kirill Smelkov k...@mns.spb.ru writes:
8
From: Kirill Smelkov k...@mns.spb.ru
Subject: [PATCH v2 1/2] tree-diff: rework diff_tree() to generate diffs for
multiparent cases as well
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The last
Previously diff_tree(), which is now named __diff_tree_sha1(), was
generating diff_filepair(s) for two trees t1 and t2, and that was
usually used for a commit as t1=HEAD~, and t2=HEAD - i.e. to see changes
a commit introduces.
In Git, however, we have fundamentally built flexibility in that a
Kirill Smelkov k...@mns.spb.ru writes:
+ /* until we go to it next round, .next holds how many bytes we
+ * allocated (for faster realloc - we don't need copying old
data).
+ */
+ p-next = (struct combine_diff_path *)alloclen;
I am getting
6 matches
Mail list logo
