From: Jay Soffian <jaysoffian@gmail.com>
To: "Adeodato Simó" <dato@net.com.org.es>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org, gitster@pobox.com,
Mikael Magnusson <mikachu@gmail.com>,
Joey Hess <joey@kitenet.net>
Subject: Re: [PATCH] git-clone.txt: document that pushing from a shallow clone may work
Date: Tue, 3 Mar 2009 14:27:29 -0500 [thread overview]
Message-ID: <76718490903031127v7fcec124je7292c4c465208b8@mail.gmail.com> (raw)
In-Reply-To: <20090303120856.GB15003@chistera.yi.org>
On Tue, Mar 3, 2009 at 7:08 AM, Adeodato Simó <dato@net.com.org.es> wrote:
> Well, I don't know if the set of cases where it'll work can be defined
> in detail to a point where it is useful. If it is, then sure, let's do
> it.
>
> My point is that if it will work in some cases, then the documentation
> should *acknowledge that fact*, because else people will assume the
> documentation is wrong, and believe it is intended to work, which is not
> the case.
Wy not just say "pushing into a shallow repository is not supported"
instead of "pushing into a shallow repository won't work."
j.
next prev parent reply other threads:[~2009-03-03 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:02 pushing from a shallow repo allowed? Joey Hess
2009-02-16 10:00 ` Mikael Magnusson
2009-03-03 11:33 ` [PATCH] git-clone.txt: document that pushing from a shallow clone may work Adeodato Simó
2009-03-03 11:57 ` Johannes Sixt
2009-03-03 12:08 ` Adeodato Simó
2009-03-03 19:27 ` Jay Soffian [this message]
2009-03-04 10:19 ` Adeodato Simó
2009-03-04 10:45 ` Junio C Hamano
2009-03-04 11:11 ` Johannes Schindelin
2009-03-05 0:41 ` Junio C Hamano
2009-03-04 22:22 ` Adeodato Simó
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=76718490903031127v7fcec124je7292c4c465208b8@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=dato@net.com.org.es \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=joey@kitenet.net \
--cc=mikachu@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).