From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alexandre Julliard <julliard@winehq.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: shallow clones, was Re: What's cooking in git.git (topics)
Date: Thu, 7 Dec 2006 15:59:39 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0612071557580.28348@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <87zma06ptm.fsf@wine.dyndns.org>
Hi,
On Thu, 7 Dec 2006, Alexandre Julliard wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> >> * js/shallow (Fri Nov 24 16:00:13 2006 +0100)
> >>
> >> Probably with a better documentation of its limitations and caveats,
> >> this should be mergeable to 'master'.
> >
> > The more I see the missing reaction, the less sure I am this is a sensible
> > thing to do.
>
> I'm not sure what reaction you expect, but this is something a lot of
> our occasional Wine users are requesting. The Wine full history is 80Mb,
> and that's a big download if you just want to try a quick patch. Now of
> course you won't see these users around here hacking on shallow clone,
> most likely they just went and downloaded Wine from the CVS mirror
> instead. But it's a shame to have to maintain a CVS mirror just for that
> purpose...
Sorry, I was just mumbling about the fact that I would _like_ to hear back
about successes and failures. If there are problems I want to fix them.
So, do you actually know of people who _used_ (as opposed to "tested")
shallow clones?
Ciao,
Dscho
next prev parent reply other threads:[~2006-12-07 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:19 What's cooking in git.git (topics) Junio C Hamano
2006-12-06 21:51 ` Jakub Narebski
2006-12-06 22:14 ` Junio C Hamano
2006-12-06 23:42 ` Johannes Schindelin
2006-12-07 9:03 ` Alexandre Julliard
2006-12-07 14:59 ` Johannes Schindelin [this message]
2006-12-07 16:44 ` shallow clones, was " Alexandre Julliard
2006-12-08 10:12 ` Aneesh Kumar K.V
2006-12-07 17:49 ` Andy Parkins
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=Pine.LNX.4.63.0612071557580.28348@wbgn013.biozentrum.uni-wuerzburg.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=julliard@winehq.org \
--cc=junkio@cox.net \
/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).