From: Joey Hess <joey@kitenet.net>
To: git@vger.kernel.org
Subject: pushing from a shallow repo allowed?
Date: Thu, 12 Feb 2009 17:02:54 -0500 [thread overview]
Message-ID: <20090212220254.GA1517@gnu.kitenet.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
git-clone(1):
A shallow repository has a number of
limitations (you cannot clone or fetch from it, nor push from nor
into it)
This and other documentation (shallow.txt, RelNotes-1.5.0.txt) says you
can't push from a shallow repo. But in a simple test of making a commit
to a shallow repo and pushing it out, it seems to work. AFAICS, git only
guards against pushes *into* a shallow repo, and fetching/cloning from a
shallow repository.
Are the docs out of date, or is there really still some problem
with pushing from a shallow repo?
BTW, --depth seems to be ignored when making a local clone.
This seems to have been fixed in the old shell git-clone in
d4110a9726c7cd5cda35b7dd03dc8f85fe3dff0c, was it accidentially lost
in the C version?
joey@gnu:~/src/other> git clone --depth 2 git git.shallow
Initialized empty Git repository in /home/joey/src/other/git.shallow/.git/
joey@gnu:~/src/other> cd git.shallow
joey@gnu:~/src/other/git.shallow> git-log --pretty=oneline|wc -l
17009
git version 1.5.6.5
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2009-02-16 0:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:02 Joey Hess [this message]
2009-02-16 10:00 ` pushing from a shallow repo allowed? Mikael Magnusson
2009-03-03 11:33 ` [PATCH] git-clone.txt: document that pushing from a shallow clone may work Adeodato Simó
2009-03-03 11:57 ` Johannes Sixt
2009-03-03 12:08 ` Adeodato Simó
2009-03-03 19:27 ` Jay Soffian
2009-03-04 10:19 ` Adeodato Simó
2009-03-04 10:45 ` Junio C Hamano
2009-03-04 11:11 ` Johannes Schindelin
2009-03-05 0:41 ` Junio C Hamano
2009-03-04 22:22 ` Adeodato Simó
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=20090212220254.GA1517@gnu.kitenet.net \
--to=joey@kitenet.net \
--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.