From: Tom Tromey <tromey@redhat.com>
To: rmathew@gmail.com
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Keeping Jacks Up-to-date
Date: Tue, 20 Sep 2005 14:43:00 -0000 [thread overview]
Message-ID: <m3irwv4xgs.fsf@localhost.localdomain> (raw)
In-Reply-To: <39399b9d05091923102eaf5502@mail.gmail.com>
>> Yeah. The 201 additions were not planned much.
>> Feel free to fix this stuff if you like.
Ranjit> Judging by your recent patch, and just to be clear, you'd prefer
Ranjit> the constraints to be "boxing", "staticImport", "generics", etc.
Ranjit> rather than a blanket "jsr201", right?
Actually I expect we won't gain much by having separate constraints,
most compilers just have a single 1.4/1.5 switch (gcjx has separate
switches but it isn't totally clear that this makes sense in all
circumstances -- I imagine I'll end up getting rid of those).
Tom
next prev parent reply other threads:[~2005-09-20 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 3:03 Ranjit Mathew
2005-09-17 15:03 ` Tom Tromey
2005-09-17 17:04 ` Ranjit Mathew
2005-09-19 14:49 ` Tom Tromey
2005-09-20 6:10 ` Ranjit Mathew
2005-09-20 14:43 ` Tom Tromey [this message]
2005-09-21 5:08 ` Ranjit Mathew
2005-09-22 15:47 ` Tom Tromey
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=m3irwv4xgs.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=mauve-discuss@sources.redhat.com \
--cc=rmathew@gmail.com \
/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).