From: Jan Hudec <bulb@ucw.cz>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: git@vger.kernel.org
Subject: Re: sbuild (or whatever) integration
Date: Tue, 29 May 2007 19:15:30 +0200 [thread overview]
Message-ID: <20070529171530.GB2980@efreet.light.src> (raw)
In-Reply-To: <87ps4kasku.fsf@mid.deneb.enyo.de>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
On Tue, May 29, 2007 at 11:26:41 +0200, Florian Weimer wrote:
> * Jan Hudec:
>
> > IMHO generic tools won't help you much, because every other command is Debian
> > specific.
>
> Yeah, and I mainly wanted to reuse process, not code. Thanks for your
> comments.
The process is definitely sensible. Also I mentioned the git
contrib/continuous scripts to help you schedule the builds.
Regards,
Jan
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-29 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 13:17 sbuild (or whatever) integration Florian Weimer
2007-05-21 18:15 ` Jan Hudec
2007-05-29 9:26 ` Florian Weimer
2007-05-29 17:15 ` Jan Hudec [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=20070529171530.GB2980@efreet.light.src \
--to=bulb@ucw.cz \
--cc=fw@deneb.enyo.de \
--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).