From: "Marco Costalba" <mcostalba@gmail.com>
To: "Jan Hudec" <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [QGIT RFC] Unit tests for QGit
Date: Sun, 17 Aug 2008 16:46:34 +0100 [thread overview]
Message-ID: <e5bfff550808170846y522cc6a8w59b696be39df311b@mail.gmail.com> (raw)
In-Reply-To: <20080808211318.GA4396@efreet.light.src>
On Fri, Aug 8, 2008 at 10:13 PM, Jan Hudec <bulb@ucw.cz> wrote:
>
> I've already done the later (have patch series ready), but I am now thinking
> that I should probably redo it the first way. What do you think. Does it make
> sense to do that?
>
Could you please post somewhere the patches ?
Better yet to fork from http://repo.or.cz/w/qgit4.git and set up your
tree on http://repo.or.cz/ host (it's easy and fast, thanks Peter :-)
I can check that and eventually pulling from that.
As a general rule if you have already done a good chunk of work with
unit test patches I would avoid to ask you to redo in a different way,
so I would say it does not make a lot of sense to me at least before
looking at the code.
Marco
P.S: I have played a bit with qmake some time ago (to set-up the
double build environment Windows/Linux) so perhaps I could help you in
finding some useful trick to avoid the cons regarding .pro files you
posted. But of course I first need to see the patches.
next prev parent reply other threads:[~2008-08-17 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 21:13 [QGIT RFC] Unit tests for QGit Jan Hudec
2008-08-08 23:00 ` Benjamin Sergeant
2008-08-10 7:55 ` Jan Hudec
2008-08-17 8:57 ` Marco Costalba
2008-08-17 14:15 ` Jan Hudec
2008-08-17 15:46 ` Marco Costalba [this message]
2008-08-17 19:58 ` Jan Hudec
2008-08-17 20:30 ` Marco Costalba
2008-08-18 18:00 ` Jan Hudec
2008-08-19 14:53 ` Marco Costalba
2008-08-27 20:18 ` Jan Hudec
2008-08-28 11:29 ` Marco Costalba
2008-08-28 15:31 ` Karl Hasselström
2008-08-28 18:54 ` Marco Costalba
2008-08-28 22:01 ` Jan Hudec
2008-08-29 7:01 ` Marco Costalba
2008-08-28 22:18 ` Karl Hasselström
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=e5bfff550808170846y522cc6a8w59b696be39df311b@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.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).