From: Tom Tromey <tromey@redhat.com>
To: rmathew@gmail.com
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Keeping Jacks Up-to-date
Date: Thu, 22 Sep 2005 15:47:00 -0000 [thread overview]
Message-ID: <m3slvxw1oe.fsf@localhost.localdomain> (raw)
In-Reply-To: <39399b9d05092022082b9094a3@mail.gmail.com>
Ranjit> So we should just have a single "jls3" (or whatever) constraint
Ranjit> to cover all these?
Yes, I think so.
Tom
prev parent reply other threads:[~2005-09-22 15:47 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
2005-09-21 5:08 ` Ranjit Mathew
2005-09-22 15:47 ` Tom Tromey [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=m3slvxw1oe.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).