diff options
author | Jeff King <peff@peff.net> | 2019-08-29 13:33:48 -0400 |
---|---|---|
committer | Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-12-04 13:20:04 +0100 |
commit | 019683025f1b14d7cb671312ab01f7330e9b33e7 (patch) | |
tree | c894009c7ed5f1ab0dd7a7a5cb2273197cdd576f /t/t4110-apply-scan.sh | |
parent | fast-import: stop creating leading directories for import-marks (diff) | |
download | tgif-019683025f1b14d7cb671312ab01f7330e9b33e7.tar.xz |
fast-import: delay creating leading directories for export-marks
When we parse the --export-marks option, we don't immediately open the
file, but we do create any leading directories. This can be especially
confusing when a command-line option overrides an in-stream one, in
which case we'd create the leading directory for the in-stream file,
even though we never actually write the file.
Let's instead create the directories just before opening the file, which
means we'll create only useful directories. Note that this could change
the handling of relative paths if we chdir() in between, but we don't
actually do so; the only permanent chdir is from setup_git_directory()
which runs before either code path (potentially we should take the
pre-setup dir into account to avoid surprising the user, but that's an
orthogonal change).
The test just adapts the existing "override" test to use paths with
leading directories. This checks both that the correct directory is
created (which worked before but was not tested), and that the
overridden one is not (our new fix here).
While we're here, let's also check the error result of
safe_create_leading_directories(). We'd presumably notice any failure
immediately after when we try to open the file itself, but we can give a
more specific error message in this case.
Signed-off-by: Jeff King <peff@peff.net>
Diffstat (limited to 't/t4110-apply-scan.sh')
0 files changed, 0 insertions, 0 deletions