From: Jens Lehmann <Jens.Lehmann@web.de>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] Teach rm to remove submodules when given with a trailing '/'
Date: Tue, 30 Oct 2012 22:28:23 +0100 [thread overview]
Message-ID: <50904677.2020308@web.de> (raw)
In-Reply-To: <508E2C05.9010109@viscovery.net>
Am 29.10.2012 08:11, schrieb Johannes Sixt:
> Am 10/29/2012 0:28, schrieb Jens Lehmann:
>> + /* Remove trailing '/' from directories to find submodules in the index */
>> + for (i = 0; i < argc; i++) {
>> + size_t pathlen = strlen(argv[i]);
>> + if (pathlen && is_directory(argv[i]) && (argv[i][pathlen - 1] == '/'))
>> + argv[i] = xmemdupz(argv[i], pathlen - 1);
>> + }
>> +
>> pathspec = get_pathspec(prefix, argv);
>> refresh_index(&the_index, REFRESH_QUIET, pathspec, NULL, NULL);
>
> That's wrong: Either move the check below get_pathspec() (which normalizes
> backslashes to forward-slashes on Windows) or use is_dir_sep().
Thanks for bringing this up.
> But isn't it somewhat dangerous to check pathspec for existance in the
> worktree without interpreting them? Think of magic pathspec syntax (that
> we do not have yet, but which may materialize sometime in the future).
I have to admit I'm not aware of magic pathspec syntax. Do you happen to
have any pointers where I could look at code doing similar things right?
next prev parent reply other threads:[~2012-10-30 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 23:28 [PATCH] Teach rm to remove submodules when given with a trailing '/' Jens Lehmann
2012-10-29 7:11 ` Johannes Sixt
2012-10-30 21:28 ` Jens Lehmann [this message]
2012-10-31 6:29 ` Johannes Sixt
2012-11-22 22:32 ` [PATCH v2] " Jens Lehmann
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=50904677.2020308@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.