All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Chen <wangchen@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	FNST-Lai Jiangshan <laijs@cn.fujitsu.com>,
	FJ-KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: tip tree clone fail
Date: Sun, 12 Oct 2008 19:28:42 +0800	[thread overview]
Message-ID: <48F1DF6A.4000900@cn.fujitsu.com> (raw)
In-Reply-To: <48EF7BC1.4000401@zytor.com>

H. Peter Anvin said the following on 2008-10-10 23:58:
> Wang Chen wrote:
>>>
>>> So http transport is wreckaged. (git version 1.6.0.1 here, Wang is using
>>> 1.5.3.x)
>>
>> My git version is 1.5.5.1, although it doesn't matter ;)
>>
> 
> http transport requires that "git update-server-info" is done after each
> push.  Otherwise, it ends up in a trainwreck.
> 
> Shawn Pierce at Google is working on a long-term solution, but in the
> meantime, if you have to use http transport, murder your IT people.
> 


So, the current solutions are:
1. Waiting for Shawn fixing it.
2. Asking Ingo to "git update-server-info" after each push.
3. Murdering our IT people.

I'd rather to do the second solution than the third one :)

Ingo, will you do "git update-server-info" after each push before
Shawn fix this problem?

  reply	other threads:[~2008-10-12 11:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48EEA714.4010205@cn.fujitsu.com>
     [not found] ` <20081010072951.GB16016@elte.hu>
     [not found]   ` <20081010083720.GA32069@elte.hu>
     [not found]     ` <alpine.LFD.2.00.0810101040200.3271@apollo>
     [not found]       ` <48EF14FC.1000801@cn.fujitsu.com>
2008-10-10  8:56         ` tip tree clone fail Thomas Gleixner
2008-10-10  8:57           ` Wang Chen
2008-10-10 15:58             ` H. Peter Anvin
2008-10-12 11:28               ` Wang Chen [this message]
2008-10-12 12:04                 ` Lars Hjemli
2008-10-12 14:15                 ` H. Peter Anvin
2008-10-12 12:41               ` Ingo Molnar
2008-10-12 12:59                 ` Miklos Vajna
2008-10-12 14:14                 ` H. Peter Anvin
2008-10-12 15:24                   ` Ingo Molnar
2008-10-12 15:36                     ` Teemu Likonen
2008-10-12 15:39                     ` Petr Baudis
2008-10-12 16:59                       ` Ingo Molnar
2008-10-12 17:37                         ` Jakub Narebski
2008-10-12 17:59                           ` Shawn O. Pearce
2008-10-13  4:09                         ` H. Peter Anvin
2008-10-13  9:40                         ` Wang Chen
2008-10-13 15:59                           ` H. Peter Anvin
2008-10-15  3:43                             ` Wang Chen
2008-10-15  5:25                               ` H. Peter Anvin
2008-10-13  4:07                       ` 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=48F1DF6A.4000900@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hpa@zytor.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.