From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, matled@gmx.net
Subject: Re: [PATCH 2/4] Add functions get_relative_cwd() and is_inside_dir()
Date: Wed, 1 Aug 2007 12:38:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708011218420.14781@racer.site> (raw)
In-Reply-To: <7vwswfbywq.fsf@assigned-by-dhcp.cox.net>
Hi,
On Tue, 31 Jul 2007, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >
> >> The function get_relative_cwd() works just as getcwd(), only that it
> >> takes an absolute path as additional parameter, returning the prefix
> >> of the current working directory relative to the given path. If the
> >> cwd is no subdirectory of the given path, it returns NULL.
> >> ...
> >> +/*
> >> + * get_relative_cwd() gets the prefix of the current working directory
> >> + * relative to 'dir'. If we are not inside 'dir', it returns NULL.
> >> + * As a convenience, it also returns NULL if 'dir' is already NULL.
> >> + */
> >> +char *get_relative_cwd(char *buffer, int size, const char *dir)
> >> +{
> >> + char *cwd = buffer;
> >> +
> >> + if (!dir || !getcwd(buffer, size))
> >> + return NULL;
> >
> > When is it not a fatal error if get_relative_cwd() is called
> > with a NULL dir parameter, or getcwd() fails?
> >
> > If there is no valid such cases, I would rather have this
> > die(), former with "BUG" and the latter with strerror(errno).
>
> Heh, it turns out that there is this lazy or clever (depending
> on the viewpoint) caller that passes the return value of
> get_git_work_tree() to this function and expect this to return
> NULL when no work tree is found.
Right. I thought I had said that (something along the lines: it is more
convenient not having to check the directory), but I probably did not.
> The callers of the is_* functions are much cleaner and in that sense the
> series is a definite improvement, but this one particular obscurity
> makes me wonder if it is replacing one unholy mess with a smaller but
> still unholy mess.
>
> Will apply on "master" and will be part of -rc4, but we probably would
> want to have a longer pre-final freeze than usual to really make sure
> this one is good.
I'll provide a patch which makes the callers of get_relative_cwd() holy,
and skip the check in get_relative_cwd(), okay?
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-01 11:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 23:23 [PATCH 0/9] work-tree clean ups Johannes Schindelin
2007-07-29 23:24 ` [PATCH 1/9] Add is_absolute_path() and make_absolute_path() Johannes Schindelin
2007-07-29 23:24 ` [PATCH 2/9] Add functions get_relative_cwd() and is_inside_dir() Johannes Schindelin
2007-07-29 23:24 ` [PATCH 3/9] white space fixes in setup.c Johannes Schindelin
2007-07-29 23:25 ` [PATCH 4/9] Clean up work-tree handling Johannes Schindelin
2007-07-29 23:25 ` [PATCH 5/9] Add set_git_dir() function Johannes Schindelin
2007-07-29 23:25 ` [PATCH 6/9] work-trees are allowed inside a git-dir Johannes Schindelin
2007-07-29 23:25 ` [PATCH 7/9] init: use get_git_work_tree() instead of rolling our own Johannes Schindelin
2007-07-29 23:26 ` [PATCH 8/9] Fix t1501 for updated work-tree logic Johannes Schindelin
2007-07-29 23:26 ` [PATCH 9/9] Fix t1500 for sane work-tree behavior Johannes Schindelin
2007-07-29 23:29 ` [UNWANTED PATCH] Die if core.bare = true and core.worktree is set Johannes Schindelin
2007-08-01 0:28 ` [PATCH 0/9] work-tree clean ups Johannes Schindelin
2007-08-01 0:28 ` [PATCH 1/4] Add is_absolute_path() and make_absolute_path() Johannes Schindelin
2007-08-01 0:29 ` [PATCH 2/4] Add functions get_relative_cwd() and is_inside_dir() Johannes Schindelin
2007-08-01 4:22 ` Junio C Hamano
2007-08-01 5:35 ` Junio C Hamano
2007-08-01 11:38 ` Johannes Schindelin [this message]
2007-08-01 15:26 ` [NOT-SERIOUS PATCH] Make get_relative_cwd() not accept NULL for a directory Johannes Schindelin
2007-08-01 16:58 ` Junio C Hamano
2007-08-01 18:26 ` [PATCH] get_relative_cwd(): clarify why it handles dir == NULL Johannes Schindelin
2007-08-01 0:29 ` [PATCH 3/4] Add set_git_dir() function Johannes Schindelin
2007-08-01 0:30 ` [PATCH 4/4] Clean up work-tree handling Johannes Schindelin
2007-08-01 5:17 ` Junio C Hamano
2007-08-01 11:46 ` Johannes Schindelin
2007-08-02 7:04 ` Junio C Hamano
2007-08-01 8:59 ` Junio C Hamano
2007-08-01 11:53 ` Johannes Schindelin
2007-08-01 0:55 ` [PATCH 0/9] work-tree clean ups Junio C Hamano
2007-08-01 1:13 ` Johannes Schindelin
2007-08-01 10:56 ` Johannes Schindelin
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=Pine.LNX.4.64.0708011218420.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=matled@gmx.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 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 NNTP newsgroup(s).