Jeff King writes:
> I probably shouldn't have included this middle patch at all, because
> the interesting thing is what happens when we do turn it off.
Actually, I think the warning is the most important part. With the
warning enabled, people should notice they are doing something
potentially w
Jeff King wrote:
> On Tue, Mar 26, 2013 at 01:21:42PM -0700, Jonathan Nieder wrote:
>> If we want this warning, would something like the following do?
>>
>> warning: You have set GIT_DIR without setting GIT_WORK_TREE
>> hint: In this case, GIT_WORK_TREE defaults to '.'
>> hint: To
On Tue, Mar 26, 2013 at 01:21:42PM -0700, Jonathan Nieder wrote:
> Jeff King wrote:
>
> > --- a/setup.c
> > +++ b/setup.c
> > @@ -437,6 +437,23 @@ const char *read_gitfile(const char *path)
> > return path;
> > }
> >
> > +static const char warn_implicit_work_tree_msg[] =
> > +N_("You have
Jeff King wrote:
> --- a/setup.c
> +++ b/setup.c
> @@ -437,6 +437,23 @@ const char *read_gitfile(const char *path)
> return path;
> }
>
> +static const char warn_implicit_work_tree_msg[] =
> +N_("You have set GIT_DIR (or used --git-dir) without specifying\n"
> + "a working tree. In Git
It can be surprising to some users that pointing GIT_DIR to
a ".git" directory does not use the working tree that
surrounds the .git directory, but rather uses the current
working directory as the working tree.
Git has always worked this way, and for the most part it has
not been a big problem. H
5 matches
Mail list logo
