From: Stephen & Linda Smith <ischis2@cox.net>
To: Git List <git@vger.kernel.org>
Cc: Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH 2/2] Add a section to the users manual documenting shallow clones.
Date: Tue, 22 Dec 2015 09:18:54 -0700 [thread overview]
Message-ID: <2514196.BYhOBJ81ik@thunderbird> (raw)
In-Reply-To: 1450750180-1811-2-git-send-email-ischis2@cox.net
On Monday, December 21, 2015 10:47:16 PM Eric Sunshine wrote:
> On Mon, Dec 21, 2015 at 9:09 PM, Stephen P. Smith <ischis2@cox.net> wrote:
> > [[repositories-and-branches]]
> > Repositories and Branches
> > =========================
> > @@ -72,6 +71,25 @@ called the <<def_working_tree,working tree>>, together with a special
> > top-level directory named `.git`, which contains all the information
> > about the history of the project.
> >
> > +[[how-to-get-a-git-repository-with-minimal-history]]
> > +How to get a Git repository with minimal history
> > +------------------------------------------------
>
> Is this a good placement for this topic? Shallow repositories are not
> heavily used, yet this placement amidst the very early and important
> topics of cloning and checking out branches assigns potentially
> significant (and perhaps unwarranted) weight to something used so
> rarely.
After some thought I think that the section should be moved near the bottom of
"Sharing development with others" since 1) that would reduce the significance
and 2) it seems that a shallow clone would normally be used for contributing to a
large project when downloading the entire history is expensive.
Should it be placed just above the Tony Luk example?
sps
next prev parent reply other threads:[~2015-12-22 16:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 2:09 [PATCH 1/2] Define the term shallow clone Stephen P. Smith
2015-12-22 2:09 ` [PATCH 2/2] Add a section to the users manual documenting shallow clones Stephen P. Smith
2015-12-22 3:47 ` Eric Sunshine
2015-12-22 18:40 ` [PATCH V2 2/2] user-manual: add section " Stephen P. Smith
2015-12-23 3:49 ` [PATCH V2 x/2] " Stephen & Linda Smith
2015-12-23 3:53 ` [PATCH V3 2/2] " Stephen P. Smith
2015-12-23 7:47 ` Eric Sunshine
2015-12-23 20:36 ` [PATCH V4 " Stephen P. Smith
2015-12-28 22:57 ` Junio C Hamano
2015-12-29 18:54 ` [PATCH V4 1/2] glossary: define the term shallow clone Stephen P. Smith
2015-12-29 18:54 ` [PATCH V5 2/2] user-manual: add section documenting shallow clones Stephen P. Smith
2015-12-29 19:24 ` Junio C Hamano
2015-12-29 21:47 ` Stephen & Linda Smith
2015-12-29 23:12 ` Junio C Hamano
2015-12-29 23:31 ` [PATCH V6 " Stephen P. Smith
2015-12-29 23:39 ` [PATCH V5 " Junio C Hamano
2015-12-30 0:03 ` [PATCH V7 " Stephen P. Smith
2015-12-29 0:00 ` [PATCH V4 " Stephen & Linda Smith
2015-12-22 16:18 ` Stephen & Linda Smith [this message]
2015-12-22 3:12 ` [PATCH 1/2] Define the term shallow clone Eric Sunshine
2015-12-22 18:38 ` [PATCH V2 1/2] glossary: define " Stephen P. Smith
2015-12-23 3:53 ` [PATCH V3 " Stephen P. Smith
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=2514196.BYhOBJ81ik@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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 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.