git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] clone: the given repository dir should be relative to $PWD

From
Junio C Hamano <junkio@cox.net>
Date
Oct 15, 2006, 01:16 UTC
Message-ID
<7v7iz274zy.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87ac3zqebs.wl@mail2.atmark-techno.com>
Yasushi SHOJI <yashi@atmark-techno.com> writes:
Show 16 quoted lines
> the repository argument for git-clone should be relative to $PWD
> instead of the given target directory.  The old behavior gave us
> surprising success and you need a few minute to know why it worked.
>
> GIT_DIR is already exported so no need to cd into $D. And this makes
> $PWD for git-fetch-pack, which is the actual command to take the given
> repository dir, the same as git-clone.
>
> Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
> ---
>
> While I'm not sure this is a feature we rely on or not, and I don't
> want to change the way people work, IMHO the old behaviour isn't
> appropriate for such higher level porcelain.
>
> The patch should be for post 1.4.3.

Well spotted. I am fairly sure that this "clone from repository relative to the target" is not intended behaviour. I'd say we should fix this before 1.4.3.

... or are there any valid reason to keep the current behaviour that I missed?

Previous: Yasushi SHOJINext: Yasushi SHOJI
Message 2 of 3 in “clone: the given repository dir should be relative to $PWD”
  1. clone: the given repository dir should be relative to $PWDYasushi SHOJI, Oct 14, 2006
  2. Junio C HamanoOct 15, 2006
  3. Yasushi SHOJIOct 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.