From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: gitk graph routing problem
Date: Mon, 5 Nov 2007 01:53:49 +0100 [thread overview]
Message-ID: <20071105005349.GA5355@steel.home> (raw)
In-Reply-To: <7vzlxtr4bu.fsf@gitster.siamese.dyndns.org>
Junio C Hamano, Mon, Nov 05, 2007 00:14:29 +0100:
> Paul Mackerras <paulus@samba.org> writes:
>
> > Alex Riesen writes:
> >
> >> To reproduce, try running in git repo:
> >>
> >> gitk 02f630448e5d48e..06ea6ba9cf46ef5
> >
> > I can't reproduce it here, as my clone of the git repo doesn't have
> > 02f630448e5d48e in it, even after updating...
>
> Heh, me neither ;-).
Stupid me. Will follow up with a link to the archived repo in private mail.
next prev parent reply other threads:[~2007-11-05 0:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 10:46 gitk graph routing problem Alex Riesen
2007-11-04 21:47 ` Paul Mackerras
2007-11-04 23:14 ` Junio C Hamano
2007-11-05 0:53 ` Alex Riesen [this message]
2007-11-05 1:17 ` Alex Riesen
2007-11-05 1:19 ` Alex Riesen
2007-12-11 22:26 ` Paul Mackerras
2007-12-14 22:29 ` Alex Riesen
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=20071105005349.GA5355@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.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).