From: Thomas Glanzmann <thomas@glanzmann.de>
To: Carlo Wood <carlo@alinoe.com>,
LKML <linux-kernel@vger.kernel.org>, GIT <git@vger.kernel.org>
Subject: Re: GIT Packages for Debian Etch
Date: Tue, 19 Jun 2007 00:08:24 +0200 [thread overview]
Message-ID: <20070618220824.GJ16393@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20070618220441.GC13538@alinoe.com>
Hello,
> after having a peek at git-core_1.5.2.1-1.dsc, and then it did build
> just fine immediately.
good point, that makes sense. I have to keep that in mind. Last time I
looked at the failed tests, saw the missing dependency and tried again.
:-)
Thomas
next prev parent reply other threads:[~2007-06-18 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:25 GIT Packages for Debian Etch Thomas Glanzmann
2007-06-18 21:27 ` Pierre Habouzit
2007-06-18 21:34 ` Thomas Glanzmann
2007-06-18 21:48 ` Carlo Wood
2007-06-18 21:56 ` Thomas Glanzmann
2007-06-18 22:03 ` Thomas Glanzmann
2007-06-18 22:04 ` Carlo Wood
2007-06-18 22:08 ` Thomas Glanzmann [this message]
2007-06-18 23:18 ` Christoph Lameter
2007-06-18 23:36 ` Roland Dreier
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=20070618220824.GJ16393@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=carlo@alinoe.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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).