* Johannes Sixt [Tue, 03 Mar 2009 12:57:22 +0100]:
> Adeodato Simó schrieb:
> > @@ -133,8 +133,10 @@ then the cloned repository will become corrupt.
> > --depth <depth>::
> > Create a 'shallow' clone with a history truncated to the
> > specified number of revisions. A shallow repository has a
> > - number of limitations (you cannot clone or fetch from
> > - it, nor push from nor into it), but is adequate if you
> > + number of limitations: you cannot clone or fetch from it,
> > + nor push into it; pushing from it into a regular repository
> > + may work correctly in some cases, but it is not guaranteed to
> > + always work. However, a shallow repository is adequate if you
> Consider a reader who wants to decide whether --depth should or can be
> used in a git clone invocation. Is the new wording helpful? If you don't
> describe those "some cases" in more detail, then we better keep the
> current wording.
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.
I think doing that is very important, and I hope I'm explaining myself
clearly.
Thanks,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
«Ara que ets la meva dona, te la fotré fins a la melsa, bacona!»
-- Terenci Moix, “Chulas y famosas”
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
