From: Junio C Hamano <gitster@pobox.com>
To: pi.songs@gmail.com
Cc: git@vger.kernel.org, rene.scharfe@lsrfire.ath.cx
Subject: Re: [PATCH1/2] Libify blame
Date: Tue, 17 Mar 2009 23:20:29 -0700 [thread overview]
Message-ID: <7v3adbmjwy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1b29507a0903172259t348cb4d5n70f5b3003b1eeb00@mail.gmail.com> (pi song's message of "Wed, 18 Mar 2009 16:59:07 +1100")
pi song <pi.songs@gmail.com> writes:
> Don't you think we should rather split up into smaller files before
> start reorganizing things?
Yes, but splitting it wrong is, eh, wrong ;-)
next prev parent reply other threads:[~2009-03-18 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 13:25 [PATCH1/2] Libify blame pi song
2009-03-18 5:41 ` Junio C Hamano
2009-03-18 5:59 ` pi song
2009-03-18 6:20 ` Junio C Hamano [this message]
2009-03-18 6:52 ` pi song
2009-03-18 7:01 ` pi song
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=7v3adbmjwy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pi.songs@gmail.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/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.