From: Bagas Sanjaya <bagasdotme@gmail.com>
To: git@vger.kernel.org
Cc: dyroneteng@gmail.com, levraiphilippeblain@gmail.com,
stolee@gmail.com, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] clone: caveat note on converting partial clone
Date: Sat, 29 May 2021 19:07:31 +0700 [thread overview]
Message-ID: <20210529120730.38472-1-bagasdotme@gmail.com> (raw)
Currently partial clones can't be converted into full clones, because
there is an issue where the remote can't send all missing objects
required.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
This patch is based on "clone: document partial clone section" by Teng
Long [1].
[1]:
https://lore.kernel.org/git/pull.745.v5.git.git.1614695133486.gitgitgadget@gmail.com/
Documentation/git-clone.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 15495675a8..551d8fd141 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -377,6 +377,10 @@ only reading commits. `git log -p -- <path>` will download blobs to
generate the patch output and git log --raw will download all blobs
that changed at recent commits in order to compute renames.
+It is currently not possible to convert partial clones into full clones,
+because there is an issue where the remote can't send all missing
+objects required. See discussion at [1].
+
:git-clone: 1
include::urls.txt[]
@@ -417,6 +421,11 @@ $ cd my-linux
$ git clone --bare -l /home/proj/.git /pub/scm/proj.git
------------
+FOOTNOTES
+---------
+
+[1]: https://lore.kernel.org/git/6422f505-29c4-bee9-e28c-b77dd831c246@gmail.com/T/#u
+
GIT
---
--
2.25.1
next reply other threads:[~2021-05-29 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 12:07 Bagas Sanjaya [this message]
2021-05-30 21:47 ` [PATCH] clone: caveat note on converting partial clone Jeff King
2021-06-01 10:46 ` Derrick Stolee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210529120730.38472-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.com \
--cc=stolee@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).