git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 11/12] documentation: replace Discussion section by link to user-manual chapter
Date: Sat, 15 Sep 2007 21:56:06 -0400	[thread overview]
Message-ID: <20070916015606.GA5118@fieldses.org> (raw)
In-Reply-To: <46E45F45.3040109@op5.se>

On Sun, Sep 09, 2007 at 11:01:57PM +0200, Andreas Ericsson wrote:
> J. Bruce Fields wrote:
>> +
>> +A git project normally consists of a working directory with a ".git"
>> +subdirectory at the top level.  The .git directory contains, among other
>> +things, a compressed object database representing the complete history
>> +of the project, a set of pointers into that history ("refs")
>
> ... into that history ("refs" - branches and tags)

I slept on it and took another look, and decided you were right; this is
what I have there now:
 
  A git project normally consists of a working directory with a ".git"
  subdirectory at the top level.  The .git directory contains, among
  other things, a compressed object database representing the complete
  history of the project, an "index" file which links that history to
  the current contents of the working tree, and named pointers into that
  history such as tags and branch heads.
 
--b.

       reply	other threads:[~2007-09-16  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11893670592247-git-send-email-bfields@citi.umich.edu>
     [not found] ` <11893670593767-git-send-email-bfields@citi.umich.edu>
     [not found]   ` <1189367059977-git-send-email-bfields@citi.umich.edu>
     [not found]     ` <11893670591013-git-send-email-bfields@citi.umich.edu>
     [not found]       ` <11893670592312-git-send-email-bfields@citi.umich.edu>
     [not found]         ` <11893670593596-git-send-email-bfields@citi.umich.edu>
     [not found]           ` <11893670592701-git-send-email-bfields@citi.umich.edu>
     [not found]             ` <11893670593670-git-send-email-bfields@citi.umich.edu>
     [not found]               ` <1189367060244-git-send-email-bfields@citi.umich.edu>
     [not found]                 ` <11893670603146-git-send-email-bfields@citi.umich.edu>
     [not found]                   ` <11893670603581-git-send-email-bfields@citi.umich.edu>
     [not found]                     ` <11893670601869-git-send-email-bfields@citi.umich.edu>
     [not found]                       ` <46E45F45.3040109@op5.se>
2007-09-16  1:56                         ` J. Bruce Fields [this message]
2007-09-16 19:38                           ` [PATCH 11/12] documentation: replace Discussion section by link to user-manual chapter Andreas Ericsson
     [not found]           ` <7vsl5nh4io.fsf@gitster.siamese.dyndns.org>
     [not found]             ` <20070909222450.GC12147@fieldses.org>
     [not found]               ` <7vbqcbuzgj.fsf@gitster.siamese.dyndns.org>
2007-09-16  2:20                 ` [PATCH 05/12] user-manual: rewrite index discussion J. Bruce Fields

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=20070916015606.GA5118@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.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.
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).