From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Allow cloning an empty repository
Date: Fri, 23 Jan 2009 17:32:05 -0500 [thread overview]
Message-ID: <20090123223205.GA11491@coredump.intra.peff.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0901230419080.3586@pacific.mpi-cbg.de>
On Fri, Jan 23, 2009 at 04:20:34AM +0100, Johannes Schindelin wrote:
> Probably. Note, however, that scripts might rely on a fail if there were
> problems.
>
> But then, scripts have no business cloning repositories (fetching, yes.
> But cloning?)
Really? I have scripts that call clone (usually followed by building the
result). Are you proposing that all scripts should "git init && git
remote add && git fetch"?
So I am strongly in favor of telling the difference between failure and
emptiness.
-Peff
next prev parent reply other threads:[~2009-01-23 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:07 [PATCH] Allow cloning an empty repository Sverre Rabbelier
2009-01-23 1:24 ` Junio C Hamano
2009-01-23 1:46 ` Sverre Rabbelier
2009-01-23 2:42 ` Johannes Schindelin
2009-01-23 2:47 ` Sverre Rabbelier
2009-01-23 3:20 ` Johannes Schindelin
2009-01-23 16:55 ` Miklos Vajna
2009-01-23 20:05 ` Johannes Schindelin
2009-01-23 22:32 ` Jeff King [this message]
2009-01-23 22:34 ` Sverre Rabbelier
2009-01-23 22:37 ` Jeff King
2009-01-23 22:39 ` Sverre Rabbelier
2009-01-24 0:28 ` Johannes Schindelin
2009-01-23 21:55 ` Mike Hommey
2009-01-24 0:26 ` http fixes, was " Johannes Schindelin
2009-01-24 9:39 ` Sverre Rabbelier
2009-01-23 23:05 ` Miklos Vajna
2009-01-24 0:33 ` Johannes Schindelin
2009-01-24 0:42 ` Sverre Rabbelier
2009-01-25 0:49 ` Miklos Vajna
2009-01-25 0:55 ` Sverre Rabbelier
2009-01-25 5:05 ` Junio C Hamano
2009-01-25 18:33 ` Sverre Rabbelier
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=20090123223205.GA11491@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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 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 NNTP newsgroup(s).