From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Unresolved issues #2 (shallow clone again)
Date: Fri, 05 May 2006 17:18:06 +0200 [thread overview]
Message-ID: <e3fqb9$hed$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0605050806370.3622@g5.osdl.org
Linus Torvalds wrote:
> So what you'd get is a _really_ cut down history that doesn't contain any
> commit history at all (just distinct "points in commit history time"), but
> that _does_ contain all the objects that the commits point to.
So we would get 'skin-deep clone' rather than 'shallow' one?
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-05 15:18 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 9:31 Recent unresolved issues Junio C Hamano
2006-04-14 16:02 ` Petr Baudis
2006-04-14 19:10 ` sean
2006-04-14 19:10 ` sean
2006-04-14 19:24 ` Petr Baudis
2006-04-14 22:56 ` Recent unresolved issues: shallow clone Carl Worth
2006-04-15 0:17 ` Johannes Schindelin
2006-04-15 0:25 ` Junio C Hamano
2006-04-15 2:11 ` Junio C Hamano
2006-04-14 23:52 ` Recent unresolved issues Linus Torvalds
2006-04-15 0:19 ` Linus Torvalds
2006-04-15 0:39 ` Linus Torvalds
2006-04-15 0:38 ` Junio C Hamano
2006-04-15 0:49 ` Linus Torvalds
2006-04-15 0:56 ` Linus Torvalds
2006-04-15 1:09 ` Linus Torvalds
2006-04-15 2:22 ` Junio C Hamano
2006-04-15 6:18 ` Junio C Hamano
2006-04-15 8:57 ` Junio C Hamano
2006-04-15 11:46 ` Johannes Schindelin
2006-04-15 16:59 ` Linus Torvalds
2006-04-15 17:17 ` Linus Torvalds
2006-04-16 8:14 ` Junio C Hamano
2006-04-15 1:35 ` Junio C Hamano
2006-04-15 4:09 ` Linus Torvalds
2006-04-15 5:06 ` Junio C Hamano
2006-05-04 8:15 ` Unresolved issues #2 Junio C Hamano
2006-05-04 8:32 ` Jakub Narebski
2006-05-04 9:14 ` Junio C Hamano
2006-05-04 9:26 ` Jakub Narebski
2006-05-04 9:58 ` Petr Baudis
2006-05-04 15:45 ` Pavel Roskin
2006-05-04 17:01 ` Unresolved issues #2 (shallow clone again) Carl Worth
2006-05-05 0:25 ` Junio C Hamano
2006-05-05 5:17 ` Martin Langhoff
2006-05-05 5:23 ` Carl Worth
2006-05-05 5:48 ` Jakub Narebski
2006-05-05 15:10 ` Linus Torvalds
2006-05-05 15:18 ` Jakub Narebski [this message]
2006-05-05 15:59 ` Linus Torvalds
2006-05-06 6:23 ` Martin Langhoff
2006-05-06 7:10 ` Junio C Hamano
2006-05-07 6:08 ` Martin Langhoff
2006-05-07 7:56 ` Jeff King
2006-05-07 15:27 ` Linus Torvalds
2006-05-08 4:24 ` Jeff King
2006-05-08 15:32 ` Linus Torvalds
2006-05-08 0:33 ` Theodore Tso
2006-05-08 0:50 ` Linus Torvalds
2006-05-08 1:26 ` Theodore Tso
2006-05-08 2:04 ` Linus Torvalds
2006-05-08 2:24 ` Theodore Tso
2006-05-08 2:42 ` Linus Torvalds
2006-05-07 8:01 ` Sergey Vlasov
2006-05-07 23:27 ` Martin Langhoff
2006-05-07 23:35 ` Junio C Hamano
2006-05-07 23:44 ` Martin Langhoff
2006-05-05 15:31 ` Carl Worth
2006-05-07 13:30 ` Jakub Narebski
2006-05-08 2:54 ` Junio C Hamano
2006-05-08 4:02 ` Jakub Narebski
2006-05-08 4:24 ` Jakub Narebski
2006-05-04 20:41 ` Unresolved issues #2 Daniel Barkalow
2006-05-04 21:33 ` Linus Torvalds
2006-05-06 5:58 ` Junio C Hamano
2006-05-06 15:26 ` Linus Torvalds
2006-05-06 15:35 ` sean
2006-05-06 15:35 ` sean
2006-05-06 16:30 ` Linus Torvalds
2006-05-06 16:53 ` sean
2006-05-06 16:53 ` sean
2006-05-06 17:20 ` Linus Torvalds
2006-05-06 21:16 ` Junio C Hamano
2006-05-06 21:33 ` Johannes Schindelin
2006-05-06 21:51 ` Linus Torvalds
2006-05-07 9:39 ` Junio C Hamano
2006-05-07 9:42 ` Junio C Hamano
2006-05-07 11:31 ` Johannes Schindelin
2006-05-07 11:38 ` Jakub Narebski
2006-05-08 2:51 ` Junio C Hamano
2006-05-07 0:41 ` Jakub Narebski
2006-05-09 11:40 ` David Woodhouse
2006-05-09 11:53 ` Bertrand Jacquin
2006-05-09 13:09 ` Nicolas Pitre
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='e3fqb9$hed$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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.