Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 1D56D184B5A8
	for <pgsql-www@postgresql.org>; Wed, 30 May 2012 11:34:42 -0300 (ADT)
Received: from mail-lpp01m010-f46.google.com ([209.85.215.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <magnus@hagander.net>) id 1SZjyy-0006gw-KI
	for pgsql-www@postgresql.org; Wed, 30 May 2012 14:34:41 +0000
Received: by lahd3 with SMTP id d3so3348608lah.19
	for <pgsql-www@postgresql.org>; Wed, 30 May 2012 07:34:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding:x-gm-message-state;
	bh=+o6oed7qhGwwk1wHMVsDS7RcVj5R83giCMWrXeKsBmQ=;
	b=P5p63uTBcGQ0iBerDZIGSLO9cSI0fik17SuFbdBZWCen6a9APD0lNGpETeb1G/JHCJ
	pgBlbM9DIqPHgPNVvAemT6gfOK59IByw6J5PUEwzWmSbgybDH7qSmGm15dYsFKKHbJJY
	KSeACnxaAO89XFt8ENVfvyUYTrDE3oo0NTsHAw0ssHhSJM0D9pxmSpTeAj+RaHOv3Zyu
	/QjsqhPUgDlNtDBdhTbEumoZWJoD92AuX6OPK/yd0XCt9PbUMaHgeYqEtq4eOnZEgL5x
	tpkjsQRs8oC8D3ARZEYiLV4VrzDvDPyRSvOuaoavdYcxMd7dCe+hzM0gOB5TI1Xka7BW
	lrhA==
MIME-Version: 1.0
Received: by 10.152.109.166 with SMTP id ht6mr15978917lab.46.1338388467159;
	Wed, 30 May 2012 07:34:27 -0700 (PDT)
Received: by 10.152.21.234 with HTTP; Wed, 30 May 2012 07:34:27 -0700 (PDT)
In-Reply-To: <29205.1338386624@sss.pgh.pa.us>
References: <20120530003133.GB24440@momjian.us>
	<CABUevEzpDFk=N9nN1FLuz8XJZgMcQ2v3aTFM-SiGcFwwByQgog@mail.gmail.com>
	<CABRT9RC2TcibvR23z9LABrvwnCYVAMsav-kUJxvcqDK2KXGWCg@mail.gmail.com>
	<29205.1338386624@sss.pgh.pa.us>
Date: Wed, 30 May 2012 16:34:27 +0200
Message-ID: 
 <CABUevEx+vPFyMO_PTZ6MN97F6wSwJKzc7DcBgrwbyZgAETfnFg@mail.gmail.com>
Subject: Re: searching for git commit hash
From: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Marti Raudsepp <marti@juffo.org>, Bruce Momjian <bruce@momjian.us>,
	PostgreSQL www <pgsql-www@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: 
 ALoCoQlm8XI1MlyYMzWApwp6CH9EfhZphhNBtvDzqx2qbzLoZd1qdzDIrecWQ9RoSctciJER2duo
X-Pg-Spam-Score: -2.6 (--)
X-Archive-Number: 201205/69
X-Sequence-Number: 20693

On Wed, May 30, 2012 at 4:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Marti Raudsepp <marti@juffo.org> writes:
>> On Wed, May 30, 2012 at 8:06 AM, Magnus Hagander <magnus@hagander.net> w=
rote:
>>> I don't believe gitweb supports searching. You'll need to pick another
>>> hash and then copy/paste on the URL.
>
>> Well there is a "search" box in the upper right corner, but I think it
>> can only search for text, not commit hashes.
>
> I have a private page containing a text box I can type the hash into.
> This is very fast and it works with hash prefixes too, which I bet
> google would not.
>
> =A0 =A0 <form action=3D"http://git.postgresql.org/gitweb"
> =A0 =A0 =A0method=3D"get" id=3D"goto-commit-id">
> =A0 =A0 =A0<input type=3D"hidden" name=3D"p" value=3D"postgresql.git" />
> =A0 =A0 =A0<input type=3D"hidden" name=3D"a" value=3D"commitdiff" />
> =A0 =A0 =A0Git Commit Hash <input type=3D"text" name=3D"h" size=3D"60" />
> =A0 =A0 </form>
>
> Dunno if enough people would use this to justify putting it on a public
> page.

Should be easy enough to add if people want it - somewhere under
www.postgresql.org/developer/ i'd assume...

--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/