git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, "'Johannes Sixt'" <j6t@kdbg.org>
Cc: "'L. E. Segovia'" <amy@amyspark.me>, <git@vger.kernel.org>
Subject: RE: [BUG] Clones from local repositories do not work correctly under Windows
Date: Fri, 12 Apr 2024 13:41:43 -0400	[thread overview]
Message-ID: <02b801da8d00$b2c5b9f0$18512dd0$@nexbridge.com> (raw)
In-Reply-To: <xmqqil0mmqpx.fsf@gitster.g>

On Friday, April 12, 2024 1:33 PM, Junio C Hamano wrote:
>Johannes Sixt <j6t@kdbg.org> writes:
>
>> alternate: C:/Temp/repoorig/.git/objects
>> alternate: /c/Temp/repoorig/.git/objects
>>
>> This is the MSYS2/Cygwin absolute path with a "drive letter".
>> Unfortunately, this kind of path is unintelligible for Git for Windows.
>> It expects absolute paths to begin with drive letter-colon or a
>> double-slash or double-backslash. For this reason, it reports "unable
>> to normalize alternate object path".
>>
>> The conclusion is: Do not use two different flavors of Git on a
>> repository that is set up with a link to an alternate repository.
>
>I do not complain to the conclusion, and I do not use Windows, but it makes
me
>wonder if there is a way to spell that full path that can be understood by
both
>implementations.  The two implementations are not incompatible in the
actual
>object contents and refnames and other things in .git/ directory, are they?
>
>In short, does MSYS2/Cygwin understand paths in "C:/Temp/..." style, and if
so,
>writing that out, even though it may not what it considers the native
format, would
>make the world a happier place.

I'm my environment (<2 month old Cygwin update), the path would be
/cygdrive/c/temp... I have not had issues using that style with git. Cygwin
itself does not understand C:\Temp (resolves to C:temp), but does understand
C:/Temp in bash and various utilities. It also understands (and expects) ~
to mean /home/user (C:\Cygwin64\home\user) in the Cygwin space, not relative
to C:\Users\user for resolving .gitconfig.


  reply	other threads:[~2024-04-12 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 17:03 [BUG] Clones from local repositories do not work correctly under Windows L. E. Segovia
2024-04-12  6:56 ` Johannes Sixt
2024-04-12 13:05   ` L. E. Segovia
2024-04-12 16:16     ` Johannes Sixt
2024-04-12 17:19       ` L. E. Segovia
2024-04-12 17:32       ` Junio C Hamano
2024-04-12 17:41         ` rsbecker [this message]
2024-04-12 20:10           ` L. E. Segovia
2024-04-12 21:53         ` Johannes Sixt

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='02b801da8d00$b2c5b9f0$18512dd0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=amy@amyspark.me \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    /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).