All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Cc: git@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	Christian Gierke <ch@gierke.de>
Subject: Re: first impressions to git
Date: Mon, 19 Sep 2005 00:11:25 +0200	[thread overview]
Message-ID: <20050918221125.GD22391@pasky.or.cz> (raw)
In-Reply-To: <20050918211855.GA1463@schottelius.org>

Dear diary, on Sun, Sep 18, 2005 at 11:18:56PM CEST, I got a letter
where Nico -telmich- Schottelius <nico-linux-git@schottelius.org> told me that...
> Adrien Beau [Sun, Sep 18, 2005 at 04:33:05PM +0200]:
> > Note that there is a problem if a Git-unaware daemon is used on the
> > server (typical in the case of HTTP and rsync). If someone pulls while
> > a push is in progress, references to not-yet-uploaded objects can be
> > retrieved.
> 
> Well, this will most likely happen often or how do you normally publish
> your famous .git-directory?

I think it should actually never happen, updating the references should
always come as the last thing in the push (or pull, for that matter)
process.

> > I'd be much obliged if you could tell me where the documentation lost you; 
> > it's really hard to document effectively without the assistance of someone 
> > who doesn't already know the program.
> 
> Well, my way was:
> 
> - find git [http://www.kernel.org/pub/software/scm/git/]
> - find documentation [http://www.kernel.org/pub/software/scm/git/docs/]
> - find step-by-step doc
>    [http://www.kernel.org/pub/software/scm/git/docs/tutorial.html]
> 
> So far so fine, than I found the git-update-index/cache thing, which confused
> me, I was not sure, whether this documentation fits only partly to git
> or absolutely not. Still, I was continuing with git-update-cache.

I believe it'd be a much more reasonable and less confusing policy for
Git to have the docs for the last release on the web. (Cogito always had
it this way, for that matter. ;-)

> > ".git/remotes" is the current one; ".git/branches" is obsolete.
> 
> Will .git/branches be complety removed later?

If that'd be the case, .git/branches is so widespread that at least
Cogito would move its content to .git/remotes automagically at some
point (it was doing such things in the past and it worked out well).

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox

  parent reply	other threads:[~2005-09-18 22:11 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
2005-09-18 22:11       ` Petr Baudis [this message]
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=20050918221125.GD22391@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=ch@gierke.de \
    --cc=git@vger.kernel.org \
    --cc=kay.sievers@vrfy.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 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.