From: Sverre Rabbelier <srabbelier@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Christian Couder <chriscool@tuxfamily.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, John Tapsell <johnflux@gmail.com>
Subject: Re: [PATCH 01/10] refs: add "for_each_bisect_ref" function
Date: Thu, 26 Mar 2009 17:54:40 +0100 [thread overview]
Message-ID: <fabb9a1e0903260954u23bd7c7aq505e016e7a5c0c29@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903261748280.12753@intel-tinevez-2-302>
Heya,
On Thu, Mar 26, 2009 at 17:52, Johannes Schindelin
<Johannes.Schindelin@gmx.de> > From the patch series' titles
(especially when they are cropped due to the
> text window being too small to fit the indented thread), it is not all
> that obvious what you want to achieve with those 10 patches.
<snip>
> Unfortunately, that does not reveal to me, quickly, what is the current
> state of affairs, and what you changed since the last time.
This is exactly what I meant to say, only worded much much better,
thanks Johannes! :)
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-26 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 4:55 [PATCH 01/10] refs: add "for_each_bisect_ref" function Christian Couder
2009-03-26 6:20 ` Sverre Rabbelier
2009-03-26 7:48 ` Christian Couder
2009-03-26 12:37 ` Sverre Rabbelier
2009-03-26 15:50 ` Michael J Gruber
2009-03-26 16:52 ` Johannes Schindelin
2009-03-26 16:54 ` Sverre Rabbelier [this message]
2009-03-27 0:41 ` Christian Couder
2009-03-27 1:32 ` sending patch sets (was: Re: [PATCH 01/10] refs: add "for_each_bisect_ref" function) Julian Phillips
2009-03-27 7:22 ` Christian Couder
2009-03-27 2:08 ` [PATCH 01/10] refs: add "for_each_bisect_ref" function Johannes Schindelin
2009-03-27 7:21 ` Christian Couder
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=fabb9a1e0903260954u23bd7c7aq505e016e7a5c0c29@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johnflux@gmail.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).