From: Johannes Sixt <j.sixt@viscovery.net>
To: "Adeodato Simó" <dato@net.com.org.es>
Cc: git@vger.kernel.org, gitster@pobox.com,
Mikael Magnusson <mikachu@gmail.com>,
Joey Hess <joey@kitenet.net>
Subject: Re: [PATCH] git-clone.txt: document that pushing from a shallow clone may work
Date: Tue, 03 Mar 2009 12:57:22 +0100 [thread overview]
Message-ID: <49AD1B22.6050201@viscovery.net> (raw)
In-Reply-To: <1236080017-13987-1-git-send-email-dato@net.com.org.es>
Adeodato Simó schrieb:
> @@ -133,8 +133,10 @@ then the cloned repository will become corrupt.
> --depth <depth>::
> Create a 'shallow' clone with a history truncated to the
> specified number of revisions. A shallow repository has a
> - number of limitations (you cannot clone or fetch from
> - it, nor push from nor into it), but is adequate if you
> + number of limitations: you cannot clone or fetch from it,
> + nor push into it; pushing from it into a regular repository
> + may work correctly in some cases, but it is not guaranteed to
> + always work. However, a shallow repository is adequate if you
Consider a reader who wants to decide whether --depth should or can be
used in a git clone invocation. Is the new wording helpful? If you don't
describe those "some cases" in more detail, then we better keep the
current wording.
-- Hannes
next prev parent reply other threads:[~2009-03-03 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:02 pushing from a shallow repo allowed? Joey Hess
2009-02-16 10:00 ` 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 [this message]
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=49AD1B22.6050201@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=dato@net.com.org.es \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
--cc=mikachu@gmail.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 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.