From: Stefan Monnier <monnier@iro.umontreal.ca>
To: git@vger.kernel.org
Subject: Re: [BUG] Destructive access to an "objects/info/alternates" repository
Date: Mon, 28 Dec 2020 15:17:01 -0500 [thread overview]
Message-ID: <jwvlfdhbsbs.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
In-Reply-To: jwv8s9hd9cg.fsf-monnier+Inbox@gnu.org
>>> git clone --reference ~otheruser/nongnu
>>
>> This doesn't appear to be a proper command, because it's missing actual
>> repository to clone, only the repository to use as reference. This is the
>> proper usage of --reference:
>>
>> git clone --reference ~/some/repo https://some/remote/repo.git
>
> Indeed, thanks:
>
> git clone --reference ~otheruser/nongnu https://git.savannah.gnu.org/r/emacs/nongnu.git
>
>> Without knowing exactly what you did, it's hard to tell what went wrong. You
>> can try running "find nongnu" to see if what you think is your own checkout is
>> actually a symlink or some combination thereof.
>
> Not sure what you mean by that.
>
> In any case, I just reproduced the problem:
FWIW, I just tried it with
git clone --shared ~otheruser/nongnu
and got the same result.
I also tried with another repository, still with the same result (tho
different pack.idx names, of course).
Stefan
next prev parent reply other threads:[~2020-12-28 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 18:50 [BUG] Destructive access to an "objects/info/alternates" repository Stefan Monnier
2020-12-28 19:00 ` Konstantin Ryabitsev
2020-12-28 19:29 ` Stefan Monnier
2020-12-28 20:17 ` Stefan Monnier [this message]
2020-12-29 15:44 ` Konstantin Ryabitsev
2021-01-03 16:50 ` Stefan Monnier
2021-01-04 13:54 ` Konstantin Ryabitsev
2021-01-04 20:47 ` Stefan Monnier
2021-01-04 21:20 ` Konstantin Ryabitsev
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=jwvlfdhbsbs.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.