Sure, but what rules or heuristics does it follow? Do we need to
post-process the results or can we simply change the test case in t1504?
It's not a thinko because I didn't think there. :) It's more a case of
mechanical refactoring resulting in confusing code. If we inline
is_absolute_path() manually there, we get the following:
assert(*comp_start == '/' || has_dos_drive_prefix(comp_start));
The loop works because DOS drive prefixes never contain slashes.
Is is_absolute_path() too forgiving on Windows, i.e. should it stop
classifying paths starting with a slash as absolute on that platform?
Good idea.
Makes sense.
René
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html