From: "Nikita V. Youshchenko" <yoush@debian.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: fetching a single commit from remote repo
Date: Sun, 10 Feb 2008 20:17:03 +0300 [thread overview]
Message-ID: <200802102017.03879@blacky.localdomain> (raw)
In-Reply-To: <alpine.LSU.1.00.0802101644540.11591@racer.site>
> Hi,
>
> On Sun, 10 Feb 2008, Nikita V. Youshchenko wrote:
> > I'm looking for a way to fetch a single snapshot, without history,
> > from remote git repository.
> >
> > I've found how to do it with a head (clone --depth 1, or fetch --depth
> > 1).
> >
> > Is it possible to do the same with non-head and non-tagged commit, if
> > only sha1 name of the commit is known?
> > Looks like fetch and fetch-pack only take ref names :(
>
> Yes, for security reasons.
I can't understand what security issues this may cause ...
If one has enough access to a repository to clone it, he already has a way
to download each and every object from there.
Ability to fetch the tree corresponding to particular commit won't add any
new permissions to him, will it?
I'm looking for a way to get a copy of a particular previous state of the
project tree, without having to download entire tree. Something similar
checking out particular svn revision.
This is going to be wrapped into a script, which is intended to be executed
by people without any knowledge of any VC system at all. Commit id could
be a parameter for such a script.
Nikita
next prev parent reply other threads:[~2008-02-10 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 15:00 fetching a single commit from remote repo Nikita V. Youshchenko
2008-02-10 16:45 ` Johannes Schindelin
2008-02-10 17:17 ` Nikita V. Youshchenko [this message]
2008-02-15 23:07 ` Jan Hudec
2008-02-10 16:48 ` Jakub Narebski
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=200802102017.03879@blacky.localdomain \
--to=yoush@debian.org \
--cc=Johannes.Schindelin@gmx.de \
--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 NNTP newsgroup(s).