From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: barkalow@iabervon.org
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: Terminology
Date: Sat, 6 Aug 2005 01:08:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0508060107350.10873@wgmdd8.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508051531400.23721@iabervon.org>
Hi,
On Fri, 5 Aug 2005, barkalow@iabervon.org wrote:
> On Fri, 5 Aug 2005, Linus Torvalds wrote:
>
> > On Fri, 5 Aug 2005, Johannes Schindelin wrote:
> >
> > > - The files under $GIT_DIR/refs record object names, and are
> > > called "refs". What is under refs/heads/ are called "heads",
> > > refs/tags/ "tags". Typically, they are either object names
> > > of commit objects or tag objects that resolve to commit
> > > objects, but a tag can point at any object.
> > >
> > > The tutorial never calls them "refs", but instead "references".
> >
> > It might be worth saying explicitly that a reference is nothing but the
> > same thing as a "object name" aka "sha1".
>
> Well, it's an object name stored in a file. This adds a layer of
> indirection and a meaningful name.
Yes.
> > So I'd vote for making the suggested definition official: "fetch" means
> > fetching the data, and "pull" means "fetch + merge".
>
> So what's the converse of "fetch" (to rename git-ssh-push to)?
> Maybe "ship"?
I actually like "push". You know, not everybody agrees that "push" is the
opposite of "pull"...
Ciao,
Dscho
next prev parent reply other threads:[~2005-08-05 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 13:52 Terminology Johannes Schindelin
2005-07-31 18:33 ` Terminology Junio C Hamano
2005-07-31 22:38 ` Terminology Johannes Schindelin
2005-08-05 14:57 ` Terminology Johannes Schindelin
2005-08-05 18:57 ` Terminology Linus Torvalds
2005-08-05 19:53 ` Terminology barkalow
2005-08-05 23:08 ` Johannes Schindelin [this message]
2005-08-05 23:07 ` Terminology Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2005-08-06 0:54 Terminology linux
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0508060107350.10873@wgmdd8.biozentrum.uni-wuerzburg.de \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).