From: Johannes Sixt <j.sixt@viscovery.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: Fetch by SHA missing
Date: Wed, 06 Oct 2010 08:02:52 +0200 [thread overview]
Message-ID: <4CAC110C.2000804@viscovery.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1010052136280.21719@obet.zrqbmnf.qr>
Am 10/5/2010 21:37, schrieb Jan Engelhardt:
> Hi,
>
>
> it is possible to select single heads/tags for download, but this does
> not work with SHA IDs as of 1.7.1.
>
> $ git fetch linus 3c06806e690885ce978ef180c8f8b6f8c17fb4b4:x
> fatal: Couldn't find remote ref 3c06806e690885ce978ef180c8f8b6f8c17fb4b4
> $ git fetch linus refs/heads/master
> remote: Counting objects: 1254, done.
> remote: Compressing objects: 100% (234/234), done.
> remote: Total 709 (delta 562), reused 602 (delta 475)
> Receiving objects: 100% (709/709), 112.41 KiB, done.
> Resolving deltas: 100% (562/562), completed with 212 local objects.
> From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
> * branch master -> FETCH_HEAD
That's by design:
http://thread.gmane.org/gmane.comp.version-control.git/73368/focus=73994
That is, when you accidentally push secret data, you can rewind your refs
on the server. Even though the objects still live on the server (until
they are garbage-collected) nobody will be able to fetch your secret stuff
even if they happen to know the SHA1.
next prev parent reply other threads:[~2010-10-06 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:37 Fetch by SHA missing Jan Engelhardt
2010-10-06 6:02 ` Johannes Sixt [this message]
2010-10-06 20:35 ` Nicolas Pitre
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=4CAC110C.2000804@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/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.