All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: .git/info/refs
Date: Fri, 26 Jan 2007 13:54:00 -0800	[thread overview]
Message-ID: <45BA7878.9000300@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701262200131.22628@wbgn013.biozentrum.uni-wuerzburg.de>

By the way, let me be the first to apologize for the emotional 
escalation.  What matters to me is that the information is cached and 
updated by a common cached information entry point (the existing 
git-update-server-index would be preferred, obviously), not where the 
information ends up.

	-hpa

  parent reply	other threads:[~2007-01-26 21:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  7:38 .git/info/refs H. Peter Anvin
2007-01-24  9:28 ` .git/info/refs Jakub Narebski
2007-01-24 15:55   ` .git/info/refs H. Peter Anvin
2007-01-24 16:02     ` .git/info/refs Johannes Schindelin
2007-01-24 16:24       ` .git/info/refs H. Peter Anvin
2007-01-24 16:38         ` .git/info/refs Johannes Schindelin
2007-01-24 16:41           ` .git/info/refs H. Peter Anvin
2007-01-24 16:52             ` .git/info/refs Johannes Schindelin
2007-01-24 17:06               ` .git/info/refs H. Peter Anvin
2007-01-24 17:25                 ` .git/info/refs Jakub Narebski
2007-01-24 17:10             ` .git/info/refs Jakub Narebski
2007-01-24 17:20               ` .git/info/refs Johannes Schindelin
2007-01-25 17:13               ` .git/info/refs H. Peter Anvin
2007-01-26 11:22                 ` .git/info/refs Jakub Narebski
2007-01-26 11:41                 ` .git/info/refs Junio C Hamano
2007-01-26 16:39                   ` .git/info/refs H. Peter Anvin
2007-01-26 17:06                     ` .git/info/refs Jakub Narebski
2007-01-26 21:09                     ` .git/info/refs Johannes Schindelin
2007-01-26 21:32                       ` .git/info/refs H. Peter Anvin
2007-01-26 21:54                       ` H. Peter Anvin [this message]
2007-01-24 20:40     ` .git/info/refs Jakub Narebski
2007-01-24 20:44       ` .git/info/refs hpa
2007-01-25  8:14         ` .git/info/refs Johannes Schindelin
2007-01-25 16:12           ` .git/info/refs H. Peter Anvin
2007-01-25 16:50             ` .git/info/refs Johannes Schindelin
2007-01-24 20:45       ` .git/info/refs hpa
2007-01-25 21:28     ` .git/info/refs Junio C Hamano
2007-01-25 21:37       ` .git/info/refs H. Peter Anvin
2007-01-25 21:51         ` .git/info/refs Junio C Hamano
2007-01-25 22:01           ` .git/info/refs H. Peter Anvin
2007-01-25 23:33             ` .git/info/refs Johannes Schindelin
2007-01-27 22:07               ` .git/info/refs H. Peter Anvin
2007-01-31 15:38                 ` .git/info/refs Santi Béjar
2007-02-01 14:03                 ` .git/info/refs Johannes Schindelin
2007-02-01 16:16                   ` .git/info/refs H. Peter Anvin
2007-02-01 16:52                     ` .git/info/refs Johannes Schindelin
2007-02-01 16:56                       ` .git/info/refs H. Peter Anvin
2007-02-01 17:32                         ` .git/info/refs Matthias Lederhofer
2007-02-01 17:51                           ` .git/info/refs H. Peter Anvin

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=45BA7878.9000300@zytor.com \
    --to=hpa@zytor.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    /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.