to participate in any such work.
--
Regards,
Mukul Gandhi
actively to any XSLT 3.0
development at Xalan.
--
Regards,
Mukul Gandhi
en the ability to do JSON transformations, and mix
> XML/JSON/XHTML, and throwing in the ability to do XQuery 3.0, it could be
> really exciting, from a functional viewpoint.
>
I agree.
--
Regards,
Mukul Gandhi
Interestingly, I can see at this location
http://svn.apache.org/repos/asf/xalan/java/branches/, following folders
xslt20 & xslt20-compiled
Any thoughts, what is the functionality currently contained in above
folders?
On Sat, May 26, 2018 at 11:41 AM, Mukul Gandhi <gandhi.mu...@gmail.com
would be pretty trivial), but I'm still interested...
>
> __
> "Your data is important to us. Please stay on the port, and your
> connection will be accepted by the next available thread."
>
--
Regards,
Mukul Gandhi
hind Saxon for example.
>
> I could see that releasing a 2.7.3 with a bug fixes would help folks.
>
> Gary
>
--
Regards,
Mukul Gandhi
g from the
> XML effort.
>
> So... I'd be glad to see it happen, I might be able to make some time to
> support the effort, but right now I don't think I can offer to help lead.
>
> __
> "Your data is important to us. Please stay on the
d.
>
> Thanks,
> Roman (on behalf of ASF board)
>
--
Regards,
Mukul Gandhi
if
that is decided.
Also, are there any technical benefits of using gitbox instead of SVN, for
Xalan-J ?
--
Regards,
Mukul Gandhi
Type: Bug
> Security Level: No security risk; visible to anyone (Ordinary
> problems in Xalan projects. Anybody can view the issue.)
> Reporter: Mohd Amir
> Assignee: Steven J. Hathaway
>
--
Regards,
Mukul Gandhi
On Mon, Apr 8, 2019 at 1:20 PM Mukul Gandhi wrote:
> Hi all,
>I've just seen below bug report, added today to the Xalan Jira.
>
> It seems that with the new team now constituted for Xalan, in the Xalan
> Jira configuration project lead should be set to Gary Gregory and addi
Hi Gary,
On Sat, Mar 23, 2019 at 9:47 AM Mukul Gandhi wrote:
> To also confirm, I guess the Xalan-J trunk still has 2.7.1 version code,
> and nothing more on that location.
>
I can see that, Xalan-J trunk has commit messages like following,
"Current V2.7.2 edits merged from main
working status;
>
>NOW, THEREFORE, BE IT RESOLVED that the Xalan PMC is re-established,
>with the persons listed immediately below appointed to serve as its
>members:
>
> * Bill Blough (billblough)
> * Roger Leigh (rleigh)
>
apache.xalan.xslt.Process.doExit(Process.java:1155)
at org.apache.xalan.xslt.Process.main(Process.java:1128)
--
Regards,
Mukul Gandhi
Hi all,
What are the minimum JDK requirements, for developing Xalan-J on the
trunk?
Also I can see that, xalan.jar provided within Xalan-J 2.7.2 release was
created with JDK 1.7.0_51 (as written in 2.7.2 xalan.jar's manifest).
--
Regards,
Mukul Gandhi
r XSL
> processors
> > out there that are free and/or FOSS?
> > - In light of Saxon, keeping Xalan-J alive seems more of an exercise in
> > maintenance. Selfishly, it would help me at work, but I might be more
> > inclined to spend my time to port to Saxon TBH, instead of waiting for
ow,
http://svn.apache.org/repos/asf/xalan/).
My above suggestions, are based on URL patterns for git repositories for
various other Apache project (ref, https://gitbox.apache.org/repos/asf)
--
Regards,
Mukul Gandhi
Hi Gary,
On Mon, Apr 8, 2019 at 8:33 PM Gary Gregory wrote:
>
> - We are looking forward to releasing 2.7.2 as a 'warm-up' to moving the
> project along again.
>
I seem to find a little typo. Within the above line, I think it should be
2.7.3.
--
Regards,
Mukul Gandhi
Hi Gary,
On Mon, Apr 8, 2019 at 8:02 PM Gary Gregory wrote:
>
> I requested the move to GitBox:
> https://issues.apache.org/jira/browse/INFRA-18179
>
Thats nice.
--
Regards,
Mukul Gandhi
.txt file
>
> command failed:
> git svn fetch
>
> Any thoughts?
>
> Yes, I have authors.txt in the current folder and it has the same content
> I used to convert https://svn.apache.org/repos/asf/xalan/pmc successfully.
>
> Thank you,
> Gary
>
--
Regards,
Mukul Gandhi
On Fri, Apr 12, 2019 at 10:13 PM Bill Blough wrote:
>
> My preference is for separate git repos.
>
I would also prefer this. I believe, it'll also be nice if, most of the
commit history from SVN is also retained after migration to Git.
--
Regards,
Mukul Gandhi
f the Travel Assistance Committee)
--
Regards,
Mukul Gandhi
al for the project if I could get permission to change values of
various fields of Jira issues on which I shall work. Currently, I don't
have such a permission.
--
Regards,
Mukul Gandhi
Hi Gary,
On Thu, May 30, 2019 at 6:01 PM Gary Gregory wrote:
> JIRA has two (2) "Mukul Gandhi"s; *Mukul*, which JIRA ID do you use?
>
I use the Jira Id mukul_gandhi.
--
Regards,
Mukul Gandhi
changes from
branch 'xalan-j_2_7_1_maint' to 'master' is important)?
--
Regards,
Mukul Gandhi
ache.org/repos/asf/xalan-site.git (the GitBox repos
for Xalan site after migration to GitBox), there are following two branches
'master' and 'git-svn'. These branches have identical content. What is the
difference between these two branches?
--
Regards,
Mukul Gandhi
as well, if in case in the future we might like to use
GitBox locations for Xalan site (therefore, we maintain the Xalan site's
SVN & GitBox sync from now itself).
Please let me know, if above mentioned steps are ok.
--
Regards,
Mukul Gandhi
hes in the
> GitHub UI than it is looking at a .patch or .diff file. There are only
> pluses IMO. The trick is getting there... which I'm not yet, I'm hoping to
> get help on the INFRA ticket...
>
> Gary
>
--
Regards,
Mukul Gandhi
:
> The xalan-c repo is ready for you to push:
>
> https://gitbox.apache.org/repos/asf/xalan-c.git
>
> Gary
>
--
Regards,
Mukul Gandhi
2016), for the repository
https://gitbox.apache.org/repos/asf/xalan-test.git?
--
Regards,
Mukul Gandhi
AM Gary Gregory wrote:
> The test repo is up: https://gitbox.apache.org/repos/asf/xalan-test.git
>
> This should conclude the migration mod the pending changes to mailing
> lists for commits and other minor changes requested by Mukul.
>
> Gary
>
--
Regards,
Mukul Gandhi
aware processors of previously mentioned languages, having support
for both XSD 1.0 and 1.1 (selectable via options, and likely XSD 1.1 as
default).
Is anyone interested about this at Xalan? And from where and how to start
this effort?
--
Regards,
Mukul Gandhi
Hi all,
I'm curious to know that, is Xalan PMC chair presently sending Xalan
monthly status reports to Apache board?
If yes, I would find it useful to see reference to the last Xalan Apache
board status report.
--
Regards,
Mukul Gandhi
re suggested below within *...*
Xalan-C++ *now* supports Microsoft Visual Studio 2019 and earlier via the
new CMake build ...
Xalan-C++ now *also* supports building with C++11, C++14 and C++17.
--
Regards,
Mukul Gandhi
On Mon, May 25, 2020 at 8:41 AM Mukul Gandhi wrote:
Xalan-C++ *now* supports Microsoft Visual Studio 2019 and earlier via the
> new CMake build ...
>
This looks ok to me.
> Xalan-C++ now *also* supports building with C++11, C++14 and C++17.
>
(maybe word 'also' doesn't look
e switching the website over to use the new
> documentation at https://apache.github.io/xalan-c/
>
>
> Kind regards,
>
> Roger
>
--
Regards,
Mukul Gandhi
>
hing significant happening these days at Xalan on this
front. Please advise Xalan team about this and drive this activity.
Hoping that, you would work (or advise others at Xalan team as appropriate)
towards achieving Apache license of the Eclipse XPath 2.0 codebase (at the
above mentioned URL and branc
XPath 3.1 implementation test cases.
If anyone has any objections or different thoughts, than above, please let
us know.
--
Regards,
Mukul Gandhi
of improvements
as well.
This work is not perfect yet, but I guess step in the right direction.
--
Regards,
Mukul Gandhi
On Wed, Feb 10, 2021 at 4:30 PM Mukul Gandhi wrote:
> Hi all,
> I've been working for a while producing a XPath 3.1 parser written in
> Java possibly for consumption by Xalan-J. I've now completed ground work
> related to that.
>
> My XPath parser distributable is located
Hi all,
I've updated few mins ago, the XPath 3.1 parser distributable at the
same location. You may get the latest archive file posted by me.
On Wed, Feb 10, 2021 at 4:30 PM Mukul Gandhi wrote:
> The mentioned parser, has been tested currently on windows platform.
>
Now the
Path 3.1 built-in functions within itself with which it can make its
checks.
Any thoughts about above points please?
--
Regards,
Mukul Gandhi
int; C++ was still trying to find it's feet at the time it was written.
>
> Anyway, there it is: if there's significant demand, I can try to make myself
> available; if there isn't, I'd rather put my effort into somethi
an-2.7.1-SNAPSHOT.jar
serializer\target\serializer-2.7.1-SNAPSHOT.jar
samples\target\samples-2.7.1-SNAPSHOT.jar
i.e, the XalanJ src code (along with samples) Maven build has worked.
Congratulations.
--
Regards,
Mukul Gandhi
-
implemented so far by XalanJ team, within XalanJ Jira.
I also IMHO wish to say that, all of this work related to XalanJ
implementation is joint work by XalanJ team.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr
s the XalanJ XSLT 3.0 and XPath 3.1
functional implementations.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
e predictable.
Thanks for your perspective, about these issues.
I've a strong feeling that, our work on XalanJ dev repos branch
xalan-j_xslt3.0, has high chances to achieve very good XSLT 3.0 and
XPath 3.1 conformance, in due course.
--
Regards,
Mukul Gandhi
---
J's XNodeSet, since lot
of XalanJ functionality is already using that. And we need to have
something else as well, to handle an XDM heterogeneous sequence
(having ResultSequence class, helps us achieve that).
--
Regards,
Mukul Gandhi
location [2] and [3].
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
RCs
for review by XalanJ team, for the above mentioned XalanJ proposed
release packages.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h
javax.servlet
>servlet-api
>2.5
>provided
>
>
>
>xerces
>xercesImpl
> 2.12.2
>
>
>
>xml-apis
>xml-apis
>1.4.01
>
>
>
>
n:fold-right, fn:for-each-pair, fn:sort, fn:codepoints-to-string,
fn:string-to-codepoints, fn:compare, fn:codepoint-equal, fn:empty,
fn:exists, fn:head, fn:tail, fn:insert-before, fn:remove, fn:reverse,
fn:subsequence, fn:unordered, fn:parse-xml, fn:parse-xml-fragment,
fn:avg, fn:max, fn:min, fn:co
XPath 3.1 processor can be shared between XSLT 3.0
and XQuery (3.1 is latest version of XQuery) processors.
IMHO, XalanJ can release XSLT 3.0 and XPath 3.1 processors,
independently of releasing an XQuery processor.
--
Regards,
Muk
thread).
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
s like following : xml_elem gt current-date() where an XML
element xml_elem has a run-time type annotation of xs:date by virtue
of an XML element xml_elem been validated by an XML schema).
--
Regards,
Mukul Gandhi
-
To unsubscribe,
-j_xslt3.0 :
https://drive.google.com/file/d/1RGKqMwLRN1UBlk9GrlAnW82lNqk1WMrf/view?usp=drive_link.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
ou've made.
Having written, all of the above mentioned points about XalanJ's XSLT
3.0 and XPath 3.1 current dev implementations, I wish to say that, I
like very much (and consider useful as well) XSLT 1.0 and XalanJ's
implementation of that.
nyone has issues, handling volume of mails on this mailing list,
please configure appropriate filters and rules on your mail client.
IMHO, handling such issues, is expected to be solved by the mail
subscribers of this list.
--
Regar
implementation on dev repos branch
xalan-j_xslt3.0, and suggest a fix for above cited implementation
issues, that'll be great and shall be helpful to the XalanJ project.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-
will be
appreciated.
On Sat, Oct 14, 2023 at 4:55 PM Mukul Gandhi wrote:
> There seems to be a codebase implementation issue on the, XalanJ
> dev repos branch xalan-j_xslt3.0, as described below.
>
> Please consider the following XSLT 3.0 stylesheet,
>
> http://www.w3.org/
me on your fair priority, to take XalanJ Maven build
process further.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
all actually, as a XalanJ team)
over the XalanJ release 3.0-alpha1 that you've suggested, from the
xalan-java repos's branch xalan-j_xslt3.0, and shall share my thoughts
on this list.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail:
ures,
have been implemented within xalan-dev repos's branch xalan-j_xslt3.0.
If there are suggestions from, you and others about these XalanJ
implementation aspects, that shall be nice to know.
--
Regards,
Mukul Gandhi
-
To unsubs
lt (Maven, Ant), and try to share
that with us. Then the XalanJ team may work to achieve the objectives
of the XalanJ release plan.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
] specified above, at the mentioned
branch, that shall be helpful.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
.
Perhaps, any commit to XalanJ's git repos, should show the name of
user who did the commit, and not the generic name like xercesj.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional
hich I think is the current status quo for this
point (ref, the jira issue
https://issues.apache.org/jira/browse/XALANJ-2601).
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional co
he CVE fix with
> 1.5 bytecode would not be harder than 1.8, and it would help a broader set of
> users.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
Hi Gary,
On Mon, Jul 25, 2022 at 4:18 PM Gary Gregory wrote:
>
> I agree that in general we should NOT use these types of accounts for commits.
Thanks, for reply and the clarification.
--
Regards,
Mukul
ect me, if I'm wrong), Xalan
Java's root git location is
https://gitbox.apache.org/repos/asf?p=xalan-java.git, and next version
of Xalan Java needs to be built from the branch xalan-j_2_7_1_maint.
--
Regards,
Mukul Gandhi
-
To unsub
would
> encourage you to try locally, building a release is a lot more than
> compiling a jar ;-) and there might not be anyone available to help
> once you hit a snag, IOW, pitfalls, and time sink.
>
> Gary (PMC Chair)
--
Regards,
Mukul Gandhi
-
smoketest.dev
Please review the new XalanJ 2.7.3 RC (i.e, RC3), and provide your comments.
Great work everyone. Here's my +1 for this RC, for the XalanJ 2.7.3 release.
On Wed, Sep 28, 2022 at 11:50 AM Mukul Gandhi wrote:
>
> Hi Joseph,
> I've analyzed about, writing a test case for this X
Hi Gary & all,
On Sun, Oct 16, 2022 at 7:08 AM Mukul Gandhi wrote:
> The signed tag associated with this RC, is located at
> https://gitbox.apache.org/repos/asf?p=xalan-java.git;a=tags (tag name
> xalan-j_2_7_2-rc5. signing key used is 7B2586A6B5E25C3D)
During my previou
[request to review, and vote]
XalanJ 2.7.3 release candidate RC5". You may download that RC, and
review it, and let us know your feedback.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
F
M Gary Gregory wrote:
>>
>> That's not where it's supposed to be. It _should_ be in
>> https://dlcdn.apache.org/xalan/xalan-j/KEYS
>>
>> We should not have KEYS files in github, that makes no sense to me.
>>
>> Gary
--
Regards,
Mukul Gandhi
Time
gpg:using RSA key 4D8FB572FB6ADCFD69CBFE0D7B2586A6B5E25C3D
gpg: Good signature from "Mukul Gandhi (CODE SIGNING KEY)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owne
y/Downloads/xalan-j_2_7_3/build.xml:1507: The following
> error occurred while executing this line:
> Error reading project file /Users/garydgregory/Downloads/test/build.xml:
> /Users/garydgregory/Downloads/test/build.xml
>
> Gary
--
Regards,
Mukul Gandhi
-
Hi Gary,
Within the previous mail, there was a typo.
I meant, The XalanJ tests _(like the "smoketest")_
Apologies for any confusion.
On Mon, Oct 31, 2022 at 9:56 AM Mukul Gandhi wrote:
> The XalanJ tests (like the "sometest")
--
Hi Gary,
I'm just curious that, did you get chance to review the XalanJ 2.7.3 RC5.
> On Sun, Oct 16, 2022 at 7:08 AM Mukul Gandhi wrote:
> During my previous mail, I had mistakenly created a tag with name
> xalan-j_2_7_2-rc5. I believe, that name should have actually been
> xalan
, we can publish XalanJ 2.7.3 release
artifacts on XalanJ github location.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
, pointing to <>
3) run the command, build fulldist
All the XalanJ tests, have passed on this mentioned release candidate.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional comma
ketest passed!
smoketest-pass:
[echo] [minitest] CONGRATULATIONS! The Smoketest passed!
Great work everyone. Here's my +1 for this XalanJ release.
On Mon, Sep 19, 2022 at 5:29 PM Mukul Gandhi wrote:
> Hi all,
>We've prepared, the XalanJ 2.7.3 release candidate, for review and
> vo
Hi all,
On Wed, Sep 21, 2022 at 2:28 PM Mukul Gandhi wrote:
> 3) Run the command "build jar" from folder xalan-test. This produces
> the file testxsl.jar within folder xalan-test/java/build.
>
> 4) Create a folder xalanj2.7.3_jardir somewhere on file system. Cop
] XalanJ 2.7.3
release candidate", that I had sent earlier today to Xalan lists, has
all the details from my point of view, that should meet the
requirements you've stated above.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e
recommending that for
distribution.
Please review, this RC. Great work everyone. Here's my +1 for this RC,
for XalanJ 2.7.3 release.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional
in between the generated pdf content.
>
> So please help on this, how do we avoid this adding - in between the generate
> data.
>
>
>
>
>
> Thanks & Regards
>
> Sindhu Mahadevappa
--
Regards,
Mukul Gandhi
-
/xalan/java;
exclude-result-prefixes="java"
version="1.0">
=>
The above XSLT stylesheet when run, produces following output:
1 => a
2 => b
3 => c
4 =>
dify the hasbtable instance [stored within an XSLT
variable] with the method call java:put($myHash, name(self::*),
string())).
IMHO, XalanJ's implementation is correct, for this use case.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mai
le for review.
On Wed, Sep 21, 2022 at 8:54 PM Mukul Gandhi wrote:
>
> Hi all,
> We've produced a new XalanJ 2.7.3 RC here
> https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/RC2/, after
> incorporating a review comment that, the XalanJ project README should
> conta
XalanJ 2.7.3's new RC.
On Tue, Oct 4, 2022 at 2:58 PM Gary Gregory wrote:
>
> Note that I plan creating a release candidate for Commons BCEL this week.
>
> Gary
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail:
ease candidate and vote.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Great work everyone. Here's my +1 for this RC.
On Tue, Oct 4, 2022 at 8:38 PM Mukul Gandhi wrote:
>
> Hi Gary,
> That should be great.
PM Gary Gregory wrote:
>
> This is SO confusing. There already was an RC1 that was voted down, right?
> The next RC should be... what? RC4 or 5, the subject of the email should have
> the RC# so we can keep track.
>
> Gary
>
>
> On Sat, Oct 15, 2022, 12:58 Mukul
amazon.com/dp/B09WJ3H657/
>
> () Plaintext Ribbon Campaign
> /\ Stamp out HTML mail!
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
g to D:\xalanj2.7.3_jardir
4) build.bat distclean
5) build.bat jar
(this shall produce, testxsl.jar)
Copy the file testxsl.jar, to folder D:\xalanj2.7.3_jardir
6) build.bat smoketest
I haven't executed these tests, from CI. I've done that, using ant
build provided by XalanJ tests repos.
--
Regards,
doing manual steps via existing
XalanJ Ant build.
It also seems to me that, instead of merging your mentioned pull
request as it is, we can take best points from your pull request and
do them manually via existing XalanJ Ant build.
--
Regards,
Mukul
, who should do that? Gary, Joseph, me, or anyone else?
I'm ready to volunteer, if provided permission.
Any comments are welcome.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional
alanJ release schedule.
--
Regards,
Mukul Gandhi
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
he XalanJ
2.7.3 release, with an Ant build along with a modification that src
zip/tar distributables include the tests. The next release after
2.7.3, might have a XalanJ Maven build.
--
Regards,
Mukul Gandhi
-
To unsubscri
Hi Gary,
On Wed, Nov 2, 2022 at 9:51 AM Mukul Gandhi wrote:
> I agree that, its a nice idea, if we include XalanJ tests as well from
> the src zip/tar distributables.
Apologies, I meant actually,
I agree that, its a nice idea, if we include XalanJ tests as well
*within* the src z
t
classpath= line within this file, perhaps suited the original author
of this file.
If we follow, the steps mentioned within the XalanJ readme file that
we've created, then XalanJ developers and users shall be able to do
all the XalanJ build and tests steps without any issues I believe.
-
1 - 100 of 560 matches
Mail list logo
