From: Jonathan Nieder <jrnieder@gmail.com>
To: Yann Dirson <ydirson@free.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v8 1/5] Introduce bulk-move detection in diffcore.
Date: Fri, 29 Oct 2010 19:26:00 -0500 [thread overview]
Message-ID: <20101030002600.GC21410@burratino> (raw)
In-Reply-To: <20101029211852.GB5695@home.lan>
Yann Dirson wrote:
> Hm, I fear too much granularity would become meaningless :)
[...]
> If the code needs to be easier to understand, I'd
> rather add some more doc, than added commits that are basically
> "useless for bisect".
Yes, the example list was probably a little overboard. Even so, the
idea was to maintain bisectability by introducing a few tests at a
time. That way, the fallout of a subfeature can easily be found with
"git bisect", among other benefits[1].
I might try it out some time soon; don't worry about it if you don't
like the idea. :)
> On Thu, Oct 28, 2010 at 08:45:40PM -0500, Jonathan Nieder wrote:
>> 1. introduce DETECT_DIRECTORY_RENAMES flag and hidden UI for it.
>
> What do you mean by "hidden UI" ?
PARSE_OPT_HIDDEN (i.e., a commandline option not tempting readers by
listing in -h).
>> Is the debugging output infrequent enough to just use a function
>> unconditionally?
>
> You mean, keep funccalls even with DEBUG_BULKMOVE is not set ? No,
> there are too many traces for that.
Yep, that's what I meant. Alas.
Will the debugging output still be useful once the code is known
to work reliably? If not, I guess we can remove it at that point
(avoiding the need to worry about patches that may introduce
debug_bulkmove(expression that does not even
typecheck);
down the line).
> Ah, sure the dst==src case can be improved. But I'm not sure
> factorizing writing NUL is worth the cost of re-computing where to put
> it when using mempcpy would avoid. Wouldn't the following be more
> adequate ?
>
> if (dst != src) {
> end = mempcpy(dst, src, slash - src + 1);
> *end = '\0';
> } else
> dst[slash - src + 1] = '\0';
> return dst;
I doubt the difference is measurable. But that looks fine (micronit:
I suppose one should put the dst == src case first in that case).
Jonathan
[1] The example that set me on this path to madness:
http://thread.gmane.org/gmane.comp.version-control.git/151086/focus=158913
next prev parent reply other threads:[~2010-10-30 0:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 22:08 [PATCH v8] Detection of directory renames Yann Dirson
2010-10-28 22:08 ` [PATCH v8 1/5] Introduce bulk-move detection in diffcore Yann Dirson
2010-10-29 1:45 ` Jonathan Nieder
2010-10-29 21:18 ` Yann Dirson
2010-10-30 0:26 ` Jonathan Nieder [this message]
2010-11-04 21:56 ` Yann Dirson
2010-11-04 21:59 ` [PATCH] " Yann Dirson
2010-11-25 10:08 ` [PATCH v8 1/5] " Ævar Arnfjörð Bjarmason
2010-11-25 15:02 ` Jonathan Nieder
2010-11-25 17:19 ` Ævar Arnfjörð Bjarmason
2010-10-28 22:08 ` [PATCH v8 2/5] Raw diff output format for bulk moves Yann Dirson
2010-10-28 22:08 ` [PATCH v8 3/5] Add testcases for the --detect-bulk-moves diffcore flag Yann Dirson
2010-10-28 22:08 ` [PATCH v8 4/5] Unified diff output format for bulk moves Yann Dirson
2010-10-28 22:08 ` [PATCH v8 5/5] [WIP] Allow hiding renames of individual files involved in a directory rename Yann Dirson
2010-10-29 1:05 ` [PATCH v8] Detection of directory renames Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101030002600.GC21410@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=ydirson@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).