From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: gitk-1.0 released
Date: Sat, 28 May 2005 13:47:27 +0200 [thread overview]
Message-ID: <20050528114727.GA1812@elte.hu> (raw)
In-Reply-To: <17036.36624.911071.810357@cargo.ozlabs.ibm.com>
another small bug: if you click into the main window _before_ the commit
list has been fully generated (i.e. into the empty window) then all
sorts of error messages pop up. ("Cant use empty string ...")
Ingo
prev parent reply other threads:[~2005-05-28 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 13:05 gitk-1.0 released Paul Mackerras
2005-05-19 13:24 ` Ingo Molnar
2005-05-19 13:30 ` Ingo Molnar
2005-05-19 22:32 ` Paul Mackerras
2005-05-20 11:22 ` Ingo Molnar
2005-05-20 11:33 ` Ingo Molnar
2005-05-20 18:18 ` Kari Hameenaho
2005-05-20 19:07 ` Linus Torvalds
2005-05-21 6:40 ` Jon Seymour
2005-05-21 16:35 ` Linus Torvalds
2005-05-19 23:13 ` Benjamin Herrenschmidt
2005-05-20 4:55 ` Frank Sorenson
2005-05-20 1:10 ` walt
2005-05-28 11:47 ` Ingo Molnar [this message]
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=20050528114727.GA1812@elte.hu \
--to=mingo@elte.hu \
--cc=git@vger.kernel.org \
--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).