git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Miriam R." <mirucam@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <christian.couder@gmail.com>
Subject: Re: [Outreachy][PATCH] abspath: reconcile `dir_exists()` and `is_directory()`
Date: Fri, 25 Oct 2019 18:43:46 +0900	[thread overview]
Message-ID: <xmqqzhhpb1nx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAN7CjDB9mRTNRKRoE8XfLz4in5gV6pxrKrqcjLPfthDHaf20nA@mail.gmail.com> (Miriam R.'s message of "Fri, 25 Oct 2019 10:59:42 +0200")

"Miriam R." <mirucam@gmail.com> writes:

> Ok, then after discussion, finally the issue tasks would be:
>
> - Add path_exists() that will work same as file_exists(), keeping for
> now the latter.
> - Use path_exists() instead of dir_exists() in builtin/clone.c.

Sounds about right.

> And also:
> - Rename is_directory() to dir_exists(), as it is the equivalent to
> path_exists()/file_exists(), isn't it?

I wouldn't go there in the same series, if I were doing it.  I'd
expect that such a patch would be more noisy than it is worth if
done in a single step.  In order to avoid becoming a hindrance to
other topics in flight, an ideal series to do so would support the
same functionality with both old and new names, convert code that
use the old name to use the new name, possibly in multiple patches
to avoid unnecessary textual conflicts (i.e. some of these patches
made to areas that are seeing active development will be discarded
and need to be retried later when the area is more quiet) and then
finally the function wither the old name gets removed.

You would not want to mix the first two bullet points that are
relatively isolated with such a long transition.

  reply	other threads:[~2019-10-25  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  9:27 [Outreachy][PATCH] abspath: reconcile `dir_exists()` and `is_directory()` Miriam Rubio
2019-10-24 11:41 ` SZEDER Gábor
2019-10-24 18:13   ` Jeff King
2019-10-24 20:45     ` Emily Shaffer
2019-10-24 20:51       ` Jeff King
2019-10-25  2:40         ` Junio C Hamano
2019-10-24 20:57   ` Miriam R.
2019-10-25  2:45   ` Junio C Hamano
2019-10-25  8:59     ` Miriam R.
2019-10-25  9:43       ` Junio C Hamano [this message]
2019-10-25 14:47         ` Christian Couder
2019-10-25 15:23           ` Miriam R.
2019-10-26 15:30             ` Miriam R.
2019-10-26 18:05               ` Christian Couder
2019-10-26 18:42                 ` Miriam R.

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqzhhpb1nx.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mirucam@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).