Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: "L. E. Segovia" <amy@amyspark.me>
Cc: git@vger.kernel.org
Subject: Re: [BUG] Clones from local repositories do not work correctly under Windows
Date: Fri, 12 Apr 2024 08:56:46 +0200	[thread overview]
Message-ID: <2f069d1f-aa4a-4259-9cc5-dcf912f59a17@kdbg.org> (raw)
In-Reply-To: <44020a6a-707f-4505-adde-e79cda63d711@amyspark.me>

Am 11.04.24 um 19:03 schrieb L. E. Segovia:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> 
> What did you do before the bug happened? (Steps to reproduce your issue)
> 
> Under Windows 10 21H2, I cloned a Git repository off an existing local
> copy, then applied a patch to it using `git am`.

This is an imprecise description of what you did. I did my best to
follow these instructions, but could not reproduce the problem mentioned
below.

You should post the commands you have given with their output.

> 
> What did you expect to happen? (Expected behavior)
> 
> Operations on the repo like `git status` and `git log` should work out
> of the box.
> 
> What happened instead? (Actual behavior)
> 
> I keep getting this error:
> 
>> error: unable to normalize alternate object path:
> /c/Users/Amalia/.cache/cerbero-sources/librsvg-2.40.20/.git/objects

What is this .cache here?

-- Hannes


  reply	other threads:[~2024-04-12  6:57 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 [this message]
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
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=2f069d1f-aa4a-4259-9cc5-dcf912f59a17@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=amy@amyspark.me \
    --cc=git@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).