From: Junio C Hamano <junkio@cox.net>
To: Marco Costalba <mcostalba@yahoo.it>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-format-patch + git-applymbox small issue
Date: Wed, 17 Aug 2005 12:26:15 -0700 [thread overview]
Message-ID: <7vll30wejs.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050817175452.84541.qmail@web26306.mail.ukl.yahoo.com> (Marco Costalba's message of "Wed, 17 Aug 2005 10:54:51 -0700 (PDT)")
Marco Costalba <mcostalba@yahoo.it> writes:
>>revision::
>> A particular state of files and directories which was stored in
>> the object database. It is referenced by a commit object.
>>
>>commit object::
>> An object which contains the information about a particular
>> revision, such as parents, committer, author, date and the
>> tree object which corresponds to the top directory of the
>> stored revision.
> So 'revision' is the struct and 'commit object' the pointer ;-)
It would be more like "revision" is a concept represented (not
"referenced") by a commit object.
>>repository::
>> A collection of refs together with an object database containing
>> all objects, which are reachable from the refs. A repository can
>> share an object database with other repositories.
>>
>
> In a lot of git documentation, starting from the tutorial, it is used 'git archive'
> but peraphs 'repository' is more a standard definition for an SCM archive.
> Just archive peraphs is too generic, also a tarball is an archive :-)
Agreed. I personally think the word "archive" on this list came
from people who have some degree of tla background. CVS and SVN
people would have said repository.
next prev parent reply other threads:[~2005-08-17 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 17:54 git-format-patch + git-applymbox small issue Marco Costalba
2005-08-17 19:26 ` Junio C Hamano [this message]
2005-08-17 19:53 ` Johannes Schindelin
2005-08-17 19:55 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 17:18 Marco Costalba
2005-08-17 17:32 ` Johannes Schindelin
2005-08-17 19:23 ` Junio C Hamano
2005-08-17 19:51 ` Johannes Schindelin
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=7vll30wejs.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
/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).