git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: first impressions to git

From
Petr Baudis <pasky@suse.cz>
Date
Sep 18, 2005, 22:11 UTC
Message-ID
<20050918221125.GD22391@pasky.or.cz>
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...

Show 8 quoted lines
> 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.

Show 14 quoted lines
> > 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
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 11 in “first impressions to git”
  1. Nico -telmich- SchotteliusSep 18, 2005
  2. Petr BaudisSep 18, 2005
  3. Daniel BarkalowSep 18, 2005
  4. Junio C HamanoSep 18, 2005
  5. Nico -telmich- SchotteliusSep 18, 2005
  6. Kay SieversSep 18, 2005
  7. Junio C HamanoSep 18, 2005
  8. Petr BaudisSep 18, 2005
  9. Junio C HamanoSep 18, 2005
  10. Linus TorvaldsSep 18, 2005
  11. Sven VerdoolaegeSep 19, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.