git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Klavins" <klavins-ooduxAEi7gXtt0EhB6fy4g@public.gmane.org>
To: msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [ANNOUNCE] qgit2.1rc1_win.exe
Date: Thu, 27 Dec 2007 00:37:51 +0100	[thread overview]
Message-ID: <fkuoko$1vg$1@ger.gmane.org> (raw)
In-Reply-To: <e5bfff550712261523g7aab6e76nd37257e7b21d1653-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


> Just a question. How about using the auto-extract zip I advertise in
> this thread? With this both Qt and qgit are already compiled and
> should be ready to go.

I did use your auto-extract utility, and it worked as advertised, thanks. 
Just as an aside, I think it would be better for it to also package git 
(msysgit version), so there's no need to search for git and pre-download it.

But being and old engineer at heart, I had to understand how to build qgit 
from scratch, and not being at all familiar with Qt, it was difficult to get 
it working, thus I wrote the note just in case others were having similar 
difficulties. I appreciate your clarification of the build steps.

Do you think it's worthwhile adding this info into your README?

------------------------------------------------------------------------
 Peter Klavins 

      parent reply	other threads:[~2007-12-26 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-24  9:13 [ANNOUNCE] qgit2.1rc1_win.exe Marco Costalba
     [not found] ` <e5bfff550712240113y4acdaa11y3483705172a5980e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-26 21:22   ` Peter Klavins
2007-12-26 23:23     ` Marco Costalba
     [not found]       ` <e5bfff550712261523g7aab6e76nd37257e7b21d1653-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-26 23:37         ` Peter Klavins [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='fkuoko$1vg$1@ger.gmane.org' \
    --to=klavins-ooduxaei7gxtt0ehb6fy4g@public.gmane.org \
    --cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=msysgit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).