git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: 'mail' link on http://repo.or.cz/w/git.git no workee?
Date: Fri, 16 Jan 2009 03:24:08 +0100	[thread overview]
Message-ID: <20090116022408.GG12275@machine.or.cz> (raw)
In-Reply-To: <alpine.DEB.1.00.0901160315170.3586@pacific.mpi-cbg.de>

On Fri, Jan 16, 2009 at 03:17:14AM +0100, Johannes Schindelin wrote:
> On Thu, 15 Jan 2009, Junio C Hamano wrote:
> 
> > Petr Baudis <pasky@suse.cz> writes:
> > 
> > >> That is, it links to marc (not gmane?) but finds no matches...
> > >
> > >   what mailing list post should it point to?
> 
> I found gmane to be much nicer to click through than marc.

IIRC I found no way to actually make a gmane link since it requires POST
query for the searches or something.

> > I think Dscho's point is that you shouldn't be generating these links 
> > that lead to nowhere ;-).
> 
> Almost.
> 
> I wondered what the point was, and I would _welcome_ links that pointed to 
> the mails containing the patches (identified either by patch ids or by 
> manual editing; best would be to have both methods at the same time).

Well, but you already have that, or at least an approximation. Do you
think the approximation is inadequate? I would expect linking to a
commit showing the inadequacy - I don't see how a false positive is
inadequate at all, actually; even if we had a separate database with the
mapping, for no records I think falling back to linking to a mailing
list search still makes more sense than showing no link.

I was not actually planning to carry the patch over the next gitweb
update since I got no feedback on it (IIRC) since I implemented it.

-- 
				Petr "Pasky" Baudis
The average, healthy, well-adjusted adult gets up at seven-thirty
in the morning feeling just terrible. -- Jean Kerr

  reply	other threads:[~2009-01-16  2:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 15:53 'mail' link on http://repo.or.cz/w/git.git no workee? Johannes Schindelin
2009-01-16  1:54 ` Petr Baudis
2009-01-16  1:59   ` Junio C Hamano
2009-01-16  2:17     ` Johannes Schindelin
2009-01-16  2:24       ` Petr Baudis [this message]
2009-01-16  2:32         ` Jacob Helwig
2009-01-16  2:41           ` Junio C Hamano
2009-01-16  2:43         ` Junio C Hamano
2009-01-16 11:27         ` Johannes Schindelin
2009-01-16 11:37         ` Johannes Schindelin
2009-01-17 15:19           ` Johannes Schindelin
2009-01-16  9:03   ` Jens Seidel

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=20090116022408.GG12275@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).