Victoria Dye <vdye@xxxxxxxxxx> writes:
>> +static void normalize_object_dir(void)
>> +{
>> + if (!opts.object_dir)
>> + opts.object_dir = get_object_directory();
>> + else
>> + opts.object_dir = real_pathdup(opts.object_dir, 1);
>> +}
>> +
>
> Rather than copy the 'normalize_object_dir()' calls to every subcommand, you
> could "centralize" this by making the 'object_dir' option an 'OPT_CALLBACK'
> option, something like:
>
> static struct option common_opts[] = {
> OPT_CALLBACK(0, "object-dir", &opts.object_dir, N_("file"),
> N_("object directory containing set of packfile and pack-index pairs"),
> normalize_object_dir),
> OPT_END(),
> };
>
> It would require changing the function signature of 'normalize_object_dir'
> to match what's shown in 'Documentation/technical/api-parse-options.txt',
> and it potentially needs prefix handling similar to what's done in
> parse-options.c:get_value() (which internally calls 'fix_filename()' for
> filename opts), but I think it's probably worth reducing duplication here
> and avoiding the need to add 'normalize_object_dir()' to any new subcommand
> in the future.
Good suggestion. Thanks, both, for taking care of this.
Are there other places that we take end-user input and treat it as a
pathname without necessary normalization, I wonder. The codepath
fixed by this series is relatively new, and I am not surprised such
a bug was still there and hopefully it was an isolated remaining bug.
