git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alex Blewitt <Alex.Blewitt@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial
Date: Mon, 27 Apr 2009 13:31:33 -0700	[thread overview]
Message-ID: <20090427203133.GG23604@spearce.org> (raw)
In-Reply-To: <loom.20090426T120010-583@post.gmane.org>

Alex Blewitt <Alex.Blewitt@gmail.com> wrote:
> Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
> > On Sun, 26 Apr 2009, Johannes Schindelin wrote:
> > > On Sun, 26 Apr 2009, Paolo Ciarrocchi wrote:
> > > > On 4/26/09, Jakub Narebski <jnareb <at> gmail.com> wrote:
> > > > 
> > > > > Perhaps it is time to restart work on _"smart" HTTP protocol_?
> > > > 
> > > > wasn't Shawn working on it?

Errh, uhm, yes, I had planned to work on it.  I failed to find
the time.  Gerrit Code Review and the necessary patches to JGit
have basically sucked up any time that I have, for anything.  Oh,
and so has "repo", the hack^W^W^W^tool Android uses to manage its
forrest of 140+ Git repositories.

> > > GIVE HIM A BREAK!
> > 
> > Sorry.  While it reflects exactly what I felt reading your mail, I should 
> > have phrased it like this:
> > 
> > 	Don't ask what Shawn can do for you.  Ask what you can do for 
> > 	Shawn.
> 
> It's something I raised a while ago with the eclipse.egit discussion; I'm happy
> to step forward and see  what I can do to improve the HTTP access, since I 
> think that's critical for adoption in organizations  who, through no fault of 
> the end user, are either not directly connected to the internet or have to go 
> via HTTP proxies due to firewall limitations.

I'm quite looking forward to this.  I'm thrilled to see another
person is interested in better HTTP support, and is trying to
work on it.

-- 
Shawn.

  reply	other threads:[~2009-04-27 20:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26  5:03 Google Code: Support for Mercurial and Analysis of Git and Mercurial Christian Couder
2009-04-26  7:12 ` Michael Witten
2009-04-26  8:16 ` Jakub Narebski
2009-04-26  8:23   ` Paolo Ciarrocchi
2009-04-26 10:07     ` Johannes Schindelin
2009-04-26 10:16       ` Jakub Narebski
2009-04-26 10:18       ` Johannes Schindelin
2009-04-26 12:02         ` Alex Blewitt
2009-04-27 20:31           ` Shawn O. Pearce [this message]
2009-04-26 10:21       ` Paolo Ciarrocchi
2009-04-26  9:21   ` Matthias Andree
2009-04-26 10:09     ` Jakub Narebski
2009-04-26 11:47       ` Matthias Andree
2009-04-26 19:57       ` Jakub Narebski
2009-04-26 14:54   ` A Large Angry SCM
2009-04-26 16:45     ` Michael Witten
2009-04-26 16:56     ` Johannes Schindelin
2009-04-26 17:33       ` A Large Angry SCM
2009-04-26 17:45         ` Johannes Schindelin
2009-04-26 18:00           ` A Large Angry SCM
2009-04-26 18:59   ` James Cloos
2009-04-26 10:13 ` Johannes Schindelin
2009-04-26 16:47   ` Michael Witten
2009-04-26 22:24   ` Miles Bader
2009-04-27 21:15   ` Shawn O. Pearce
2009-04-30  0:00     ` Mark Lodato

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=20090427203133.GG23604@spearce.org \
    --to=spearce@spearce.org \
    --cc=Alex.Blewitt@gmail.com \
    --cc=git@vger.kernel.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).