From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@ucw.cz>
Cc: GIT Mailing List <git@vger.kernel.org>
Subject: Re: Problem with cg-diff <file>
Date: Mon, 30 May 2005 00:54:13 -0700 [thread overview]
Message-ID: <7vfyw55eu2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050530003242.GA1036@pasky.ji.cz> (Petr Baudis's message of "Mon, 30 May 2005 02:32:42 +0200")
>>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:
PB> Ok, so this is what you get when you mix: sleepiness, performing only
PB> mental experiments not verified in practice, and inattentive reading of
PB> the code.
PB> I'm sorry for bothering. Instruct yourself from my bad example, please.
PB> :-)
If you forbid people to ask for help when the person who is
asked might feel the question groundless or based on "only
mental experiments not verified in practice and inattentive
reading of the code", the value to have a community diminishes.
We ask questions and ask for help because we know others know
more about things we do not know offhand, not necessarily
because we would not ever be able to figure them out ourselves.
If you know somebody else would know the answer immediately for
something that may take you a day or so to figure out, asking
for help is the right thing to do --- your time is better spent
on what you do best (e.g. improving Cogito). I should not feel
bothered by your questions, and I am certainly not feeling
bothered at all (well, at least until seeing the last sentence,
and wondering what you really meant ;-)).
Always glad to be of help.
next prev parent reply other threads:[~2005-05-30 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 23:15 Problem with cg-diff <file> Marcel Holtmann
2005-05-29 23:38 ` Petr Baudis
2005-05-30 0:19 ` Junio C Hamano
2005-05-30 0:32 ` Petr Baudis
2005-05-30 7:54 ` Junio C Hamano [this message]
2005-05-30 8:36 ` Petr Baudis
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=7vfyw55eu2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.