From: Andrew Haley <aph@redhat.com>
To: Thomas <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve patches.
Date: Tue, 13 Apr 2004 14:30:00 -0000 [thread overview]
Message-ID: <16507.63791.746420.624801@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <200404131556.13282.zander@javalobby.org>
Thomas writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 13 April 2004 15:19, you wrote:
> > David Lichteblau writes:
> > > Unless I misunderstood Thomas' question, he could not compile all
> > > of Mauve because his script tried to compile _everything_, as
> > > opposed to those files usually chosen by the standard build system.
> > > I would find it a little confusing if Mauve provided two build
> > > systems, one which uses tags and one which does not.
> >
> > Yes. I suppose Thomas' Ant script should do the right thing with
> > respect to the tags.
>
> The selecting of files based on some 'tag in their content is quite easy in
> ant; its a standard target.
> I could add an ant-build target that builds based on tags.
Excellent. Now I feel not so bad for being slow to commit...
Andrew.
next prev parent reply other threads:[~2004-04-13 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 7:55 Thomas
2004-04-06 8:47 ` Michael Koch
2004-04-08 19:34 ` Thomas Zander
2004-04-08 19:50 ` Michael Koch
2004-04-08 19:58 ` Andrew Haley
2004-04-11 6:48 ` Thomas Zander
2004-04-11 12:22 ` David Lichteblau
2004-04-11 17:20 ` Thomas Zander
2004-04-11 18:57 ` David Lichteblau
2004-04-11 19:37 ` Thomas Zander
2004-04-12 4:12 ` C. Brian Jones
2004-04-16 20:23 ` Anthony Green
2004-04-16 22:57 ` C. Brian Jones
2004-04-13 13:22 ` Andrew Haley
2004-04-13 13:55 ` Thomas
2004-04-13 14:30 ` Andrew Haley [this message]
2004-04-13 17:14 ` Thomas Zander
2004-04-13 17:45 ` Andrew Haley
2004-04-13 18:59 ` Thomas Zander
2004-04-14 9:56 ` Andrew Haley
2004-04-14 0:09 ` Bill McFadden
2004-04-15 22:56 ` Mark Wielaard
2004-04-17 14:45 ` Thomas Zander
2004-04-11 15:56 ` Archie Cobbs
2004-04-15 21:10 ` Mark Wielaard
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=16507.63791.746420.624801@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=mauve-discuss@sources.redhat.com \
--cc=zander@javalobby.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 read-only IMAP folder(s) and NNTP newsgroup(s).