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

Re: [PATCH v2 0/2] clone: simplify progress message

From
PHPete Harlan <pgit@pcharlan.com>
Date
May 9, 2010, 23:10 UTC
Message-ID
<4BE74101.20900@pcharlan.com>
In-Reply-To
<7vr5lk90yg.fsf@alter.siamese.dyndns.org>
On 05/09/2010 03:15 PM, Junio C Hamano wrote:
Show 24 quoted lines
> Pete Harlan <pgit@pcharlan.com> writes:
> 
>> On 05/09/2010 04:02 AM, Jeff King wrote:
>>> On Sat, May 08, 2010 at 06:23:21PM -0700, Pete Harlan wrote:
>>> 
>>>> "git clone foo bar" currently reports "Cloning into
>>>> /path/to/bar/.git".  Change this message to "Cloning into bar" to more
>>>> closely match the user's expectation.
>>> 
>>> I am a little torn on this. For most users, it is just another
>>> implementation detail that makes git's output more confusing. And it is
>>> likely to be the very first git message seen by many people. But at the
>>> same time, it is telling you where the repository actually is, which is
>>> something that can help users learn about how git works.
>>> 
>>> I guess it comes down to how much detail we want to show.
>>
>> For me it isn't only a matter of detail; I find "Cloning into
>> bar/.git" misleading, since bar is getting more than a .git directory.
> 
> That is also misleading, as cloning is done into bar/.git and everything
> else happens locally as part of the checkout.
> 
> I didn't want to go into nitpicky details, but you asked for it ;-)
Fair enough :)
Show 6 quoted lines
>> Pete Harlan (2):
>>   clone: have progress report mention top level dir, not git dir
>>   clone: add bare clone to the progress message
> 
> I think the squashing these two into one patch makes quite a lot of
> sense.  Does any of the existing test need adjustments, by the way?

No, the test (t5601-clone.sh) looks for "Clon", so the new message passes that just as well.

I could add a new test that ensures that "bare repository" shows up in the message when --bare is passed if you think that's worthwhile.

--Pete
Previous: Junio C HamanoNext: Jeff King
Message 7 of 14 in “clone: have progress report mention top level dir, not git dir”
  1. clone: have progress report mention top level dir, not git dirPete Harlan, May 9, 2010
  2. Jeff KingMay 9, 2010
  3. 0/2 clone: simplify progress messagePete Harlan, May 9, 2010
  4. 1/2 clone: have progress report mention top level dir, not git dirPete Harlan, May 9, 2010
  5. 2/2 clone: add bare clone to the progress messagePete Harlan, May 9, 2010
  6. Junio C HamanoMay 9, 2010
  7. Pete HarlanMay 9, 2010
  8. Jeff KingMay 10, 2010
  9. Michael J GruberMay 10, 2010
  10. clone: report check out for non-bare clonesMichael J Gruber, May 10, 2010
  11. Junio C HamanoMay 12, 2010
  12. Michael J GruberMay 12, 2010
  13. Pete HarlanMay 10, 2010
  14. Michael J GruberMay 11, 2010

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.