From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 00/11] Build in clone
Date: Sat, 8 Mar 2008 18:03:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.1.00.0803081803250.19665@iabervon.org> (raw)
This series is getting closer to being ready, and I think a number of
the initial patches are ready. In particular, 1-3 are tests that work
unexceptionally with the current implementation, and point out
potential bugs in a C version (which I've fixed); 4-7 are changes and
additions that should be pretty uncontraversial, which later code will
need; 8 is a potentially more contraversial library feature.
9 gives API access to init-db, and may or may not be ready, although I
think it looks promising now; 10 builds in clone and probably needs
more work; and 11 adds support for figuring out what the user means
with a bundle and should probably get squashed into 10.
(Unrelated note: it might actually be good to use some sort of log
instead of shortlog in --cover-letter, at least as an option, in order
to list the contents of the series with the patch numbers and order
they have)
Daniel Barkalow (8):
Test that --reference actually suppresses fetching referenced objects
Mark the list of refs to fetch as const
Add a library function to add an alternate to the alternates file
Add a function to set a non-default work tree
Have a constant extern refspec for "--tags"
Allow for having for_each_ref() list some refs that aren't local
Provide API access to init_db()
Build in clone
Johan Herland (2):
Add test for cloning with "--reference" repo being a subset of source repo
Add a test for another combination of --reference
Johannes Schindelin (1):
Support bundles in builtin-clone
Makefile | 2 +-
builtin-clone.c | 553 +++++++++++++++++++++++++++++++++++++++++
builtin-fetch.c | 10 +-
builtin-init-db.c | 183 +++++++-------
builtin.h | 1 +
cache.h | 6 +
contrib/examples/git-clone.sh | 518 ++++++++++++++++++++++++++++++++++++++
environment.c | 6 +
git-clone.sh | 518 --------------------------------------
git.c | 1 +
refs.c | 18 ++
refs.h | 9 +
remote.c | 9 +
remote.h | 2 +
sha1_file.c | 19 ++
t/t5700-clone-reference.sh | 35 +++-
transport.c | 16 +-
transport.h | 4 +-
18 files changed, 1283 insertions(+), 627 deletions(-)
create mode 100644 builtin-clone.c
create mode 100755 contrib/examples/git-clone.sh
delete mode 100755 git-clone.sh
next reply other threads:[~2008-03-08 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 23:03 Daniel Barkalow [this message]
2008-03-08 23:15 ` [PATCH 00/11] Build in clone Johannes Schindelin
2008-03-08 23:20 ` Daniel Barkalow
2008-03-09 5:32 ` Junio C Hamano
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=alpine.LNX.1.00.0803081803250.19665@iabervon.org \
--to=barkalow@iabervon.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