From: Junio C Hamano <junkio@cox.net>
To: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Cc: git@vger.kernel.org
Subject: Re: first impressions to git
Date: Sun, 18 Sep 2005 15:09:32 -0700 [thread overview]
Message-ID: <7vk6he110j.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050918211855.GA1463@schottelius.org> (nico-linux-git@schottelius.org's message of "Sun, 18 Sep 2005 23:18:56 +0200")
Nico -telmich- Schottelius <nico-linux-git@schottelius.org> writes:
> [22:29] hydrogenium:git-core-0.99.6% ls git-update-*
> git-update-cache git-update-server-info
>
> http://www.kernel.org/pub/software/scm/git/docs/tutorial.html (v0.99.5, Aug 2005):
>
> "The first step is trivial: when you want to tell git about any changes to your working tree, you use the git-update-index program."
This is my fault. The on-line documentation on kernel.org
always follow what is in the "master" branch that is a bit ahead
of the last released version.
Also, the version number on each of the page does not
necessarily match the version of the software -- it gets updated
to reflect the version of the last update of the doc, so the
pages reachable from git.html show different versions.
But still when you saw us talk about "git-update-index" and saw
you only have "git-update-cache", you could have looked at
git.html documentation page and find out that it says the
command git-update-index was previously known as
git-update-cache.
>> .git/description is actually a gitweb feature, not a core git feature.
>> You'd only set it up for public repositories that you want to describe.
>
> That does not fit to what I see here:
>
> [22:46] hydrogenium:gpm% git-init-db
> defaulting to local storage area
> [22:46] hydrogenium:gpm% ls .git
> branches description HEAD hooks info objects refs remotes
You two are both right. Git itself does not look at
description, but just as a convenience it shows where to put
that file if you ever want to publish it from its built-in
templates.
>> ".git/remotes" is the current one; ".git/branches" is obsolete.
>
> Will .git/branches be complety removed later?
That is what the word deprecated usually means. For now both
are supported.
next prev parent reply other threads:[~2005-09-18 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 11:12 first impressions to git Nico -telmich- Schottelius
2005-09-18 14:54 ` Petr Baudis
[not found] ` <94fc236b050918073351075bb4@mail.gmail.com>
2005-09-18 21:18 ` Nico -telmich- Schottelius
2005-09-18 21:39 ` Kay Sievers
2005-09-18 22:09 ` Junio C Hamano [this message]
2005-09-18 22:11 ` Petr Baudis
2005-09-18 22:23 ` Junio C Hamano
2005-09-18 22:29 ` Linus Torvalds
2005-09-18 16:56 ` Daniel Barkalow
2005-09-18 17:31 ` Junio C Hamano
2005-09-19 19:14 ` Sven Verdoolaege
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=7vk6he110j.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nico-linux-git@schottelius.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.
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).