From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Finn Arne Gangstad <finnag@pvv.org>, git@vger.kernel.org
Subject: Re: Pushing and fetching sha1s directly
Date: Sun, 23 Dec 2007 20:04:53 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712232003470.23902@racer.site> (raw)
In-Reply-To: <7vlk7mwchm.fsf@gitster.siamese.dyndns.org>
Hi,
On Sat, 22 Dec 2007, Junio C Hamano wrote:
> Finn Arne Gangstad <finnag@pvv.org> writes:
>
> > Currently there seems to be no way of pusing a sha1 directly, or to
> > fetch a sha1 directly. When working with submodules, it is convenient
> > to be able to work with detached HEADs, so it would be good if this
> > could be supported also by fetch and push.
>
> For fetch, I would normally say "check the list archives", but it was
> very long time ago that it was proposed and discussed. It has some
> security and performance implications.
To enhance on that: sometimes you need to delete a branch in a hurry,
because you publicised some secret code/file. In that case, you do _not_
want people being able to fetch arbitrary commits.
Ciao,
Dscho
prev parent reply other threads:[~2007-12-23 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 21:13 Pushing and fetching sha1s directly Finn Arne Gangstad
2007-12-22 23:12 ` Junio C Hamano
2007-12-23 20:04 ` Johannes Schindelin [this message]
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=Pine.LNX.4.64.0712232003470.23902@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).