This is an automated email from the ASF dual-hosted git repository.
isapir pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new 3dd2328edb Allow users to add local scripts
This is an automated email from the ASF dual-hosted git repository.
isapir pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.1.x by this push:
new 08d00a4825 Allow users to add local scripts
This is an automated email from the ASF dual-hosted git repository.
isapir pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/main by this push:
new 2b34da89e1 Allow users to add local scripts
This is an automated email from the ASF dual-hosted git repository.
schultz pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit a6c9c0f3157c04326794953062a63de1d8777331
Author: Christopher Schultz
AuthorDate: Fri Feb 2 14:47:08 2024 -0500
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
commit 89df072e7d4e7bd32440683b6971d20f63fe289d
Author: Mark Thomas
AuthorDate: Wed Sep 27 14:19:25 2023 +0100
git
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
The following commit(s) were added to refs/heads/main by this push:
new ad9b4a3fb Fix git command in comment
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new bb18cb686b Update building page. Java 11 &
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new e74a357776 Update building page. Java 11 &
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 10.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.0.x by this push:
new cb24085098 Update building page. Java 11 &
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/main by this push:
new d4008c0b65 Update building page. Java 11 &
Am 21.04.2022 um 09:56 schrieb Mark Thomas:
On 20/04/2022 22:52, Rainer Jung wrote:
I currently see ERROR messages when doing git push. The push itself
seems to work and triggers eg. travis, but the error seems related
with CI. Example:
Enumerating objects: 5, done.
Counting objects: 100
On 20/04/2022 22:52, Rainer Jung wrote:
I currently see ERROR messages when doing git push. The push itself
seems to work and triggers eg. travis, but the error seems related with
CI. Example:
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2
I currently see ERROR messages when doing git push. The push itself
seems to work and triggers eg. travis, but the error seems related with
CI. Example:
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2 threads
Compressing objects: 100% (3/3
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
The following commit(s) were added to refs/heads/main by this push:
new 2133b43 Fix script so it works with current
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
commit e3259817ba2b18fc69376f6734ba01a05175a7d7
Author: Mark Thomas
AuthorDate: Thu May 27 16:35:35 2021 +0100
Tweak
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new 4e249e8 Correct Git branch used for 9.0.x
4e249e8
On 17/02/2021 18:21, Konstantin Kolinko wrote:
> ср, 17 февр. 2021 г. в 20:57, Konstantin Kolinko :
>>
>> ср, 17 февр. 2021 г. в 19:55, Mark Thomas :
>>>
>>> Hi all,
>>>
>>> If there are no objections, I plan to move the module to using gi
ср, 17 февр. 2021 г. в 20:57, Konstantin Kolinko :
>
> ср, 17 февр. 2021 г. в 19:55, Mark Thomas :
> >
> > Hi all,
> >
> > If there are no objections, I plan to move the module to using git as
> > the master and updating the infrastructure accordingly.
&g
iced that it is still
> configured to use the now defunct svn->git mirroring service.
>
> If there are no objections, I plan to move the module to using git as
> the master and updating the infrastructure accordingly.
+1 to move to Git.
IIRC we did not ask Infra to restore mirroring for this
Hi all,
I was chatting with a potential contributor to the tomcat-maven-plugin
project in the ASF-OGC-OSGeo code sprint. We wnet looking for the source
and he found an old mirror on github. I noticed that it is still
configured to use the now defunct svn->git mirroring serv
>
>>>> On 10/26/20 20:47, Konstantin Kolinko wrote:
>>>> пт, 2 окт. 2020 г. в 00:09, Mark Thomas :
>>>>>
>>>>> Hi all,
>>>>>
>>>>> The topic came up at the BoF session at the end of the Tomcat track of
>>&
:47, Konstantin Kolinko wrote:
> >> пт, 2 окт. 2020 г. в 00:09, Mark Thomas :
> >>>
> >>> Hi all,
> >>>
> >>> The topic came up at the BoF session at the end of the Tomcat track of
> >>> migrating the website from svn to git. There we
пт, 2 окт. 2020 г. в 00:09, Mark Thomas :
>>>
>>> Hi all,
>>>
>>> The topic came up at the BoF session at the end of the Tomcat track of
>>> migrating the website from svn to git. There were strong opinions both
>>> for migrating and for sticking
came up at the BoF session at the end of the Tomcat track of
> >> migrating the website from svn to git. There were strong opinions both
> >> for migrating and for sticking with svn.
> >>
> >> As a middle ground I'd like to propose we ask Infra to create a g
Konstantin,
On 10/26/20 20:47, Konstantin Kolinko wrote:
пт, 2 окт. 2020 г. в 00:09, Mark Thomas :
Hi all,
The topic came up at the BoF session at the end of the Tomcat track of
migrating the website from svn to git. There were strong opinions both
for migrating and for sticking with svn
пт, 2 окт. 2020 г. в 00:09, Mark Thomas :
>
> Hi all,
>
> The topic came up at the BoF session at the end of the Tomcat track of
> migrating the website from svn to git. There were strong opinions both
> for migrating and for sticking with svn.
>
> As a middle ground I'
On Fri, Oct 2, 2020 at 12:09 AM Mark Thomas wrote:
> Hi all,
>
> The topic came up at the BoF session at the end of the Tomcat track of
> migrating the website from svn to git. There were strong opinions both
> for migrating and for sticking with svn.
>
> As a middle groun
Hi all,
The topic came up at the BoF session at the end of the Tomcat track of
migrating the website from svn to git. There were strong opinions both
for migrating and for sticking with svn.
As a middle ground I'd like to propose we ask Infra to create a git
mirror of the svn repo.
For those
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/7.0.x by this push:
new e487719 Use a link to TestTomcat in Git
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new c08d2d4 Use a link to TestTomcat in Git
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new f95fcd2 Use a link to TestTomcat in Git
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push:
new 16181fc Use a link to TestTomcat in Git
t;, I've always understood
this
>> > as the 'master record' (I know it might be historically wrong) and I
>> > haven't seen evidences it has ever offended or deterred anyone from
>> > co
quot;master", I've always understood this
> > as the 'master record' (I know it might be historically wrong) and I
> > haven't seen evidences it has ever offended or deterred anyone from
> > contributing.
> >
> > If there is a consensus to change I suggest waiting to see what GitHub
> > p
homas a écrit :
>>
>>> Thoughts?
>>
>> I'd prefer the status-quo and keep "master", I've always
>> understood this as the 'master record' (I know it might be
>> historically wrong) and I haven't seen evidences it has ever
>> offended or deterred anyo
;
> I'd prefer the status-quo and keep "master", I've always understood this
> as the 'master record' (I know it might be historically wrong) and I
> haven't seen evidences it has ever offended or deterred anyone from
> contributing.
>
> If there is a consensus to chang
contributing.
If there is a consensus to change I suggest waiting to see what GitHub
plans to do. The "master" name is a de-facto standard for Git
repositories, and I think we should remain consistent with the new name
that will be popularized by GitHub.
That said, I have a preference for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 6/16/20 04:02, Mark Thomas wrote:
> All,
>
> You may have seen the recent discussions both inside and outside
> the ASF about the user of "master" as the name of the default git
> branch. If you haven't, the short
вт, 16 июн. 2020 г. в 11:02, Mark Thomas :
>
> All,
>
> You may have seen the recent discussions both inside and outside the ASF
> about the user of "master" as the name of the default git branch. If you
> haven't, the short version is that the name can be traced ba
at 11:02 AM Mark Thomas wrote:
>
>> All,
>>
>> You may have seen the recent discussions both inside and outside the ASF
>> about the user of "master" as the name of the default git branch. If you
>> haven't, the short version is that the name can be traced back
Hi,
On Tue, Jun 16, 2020 at 11:02 AM Mark Thomas wrote:
> All,
>
> You may have seen the recent discussions both inside and outside the ASF
> about the user of "master" as the name of the default git branch. If you
> haven't, the short version is that the name can b
+1 for main
On Tue, Jun 16, 2020 at 8:00 AM Coty Sutherland wrote:
>
> On Tue, Jun 16, 2020 at 4:02 AM Mark Thomas wrote:
>
>> All,
>>
>> You may have seen the recent discussions both inside and outside the ASF
>> about the user of "master" as
On Tue, Jun 16, 2020 at 4:02 AM Mark Thomas wrote:
> All,
>
> You may have seen the recent discussions both inside and outside the ASF
> about the user of "master" as the name of the default git branch. If you
> haven't, the short version is that the name can be trac
Am 2020-06-16 um 12:09 schrieb Mark Thomas:
On 16/06/2020 10:25, Michael Osipov wrote:
Am 2020-06-16 um 10:02 schrieb Mark Thomas:
All,
You may have seen the recent discussions both inside and outside the ASF
about the user of "master" as the name of the default git branch. If y
On 16/06/2020 10:25, Michael Osipov wrote:
> Am 2020-06-16 um 10:02 schrieb Mark Thomas:
>> All,
>>
>> You may have seen the recent discussions both inside and outside the ASF
>> about the user of "master" as the name of the default git branch. If you
>>
Am 2020-06-16 um 10:02 schrieb Mark Thomas:
All,
You may have seen the recent discussions both inside and outside the ASF
about the user of "master" as the name of the default git branch. If you
haven't, the short version is that the name can be traced back to
master/slave and its as
На вт, 16.06.2020 г. в 11:02 Mark Thomas написа:
>
> All,
>
> You may have seen the recent discussions both inside and outside the ASF
> about the user of "master" as the name of the default git branch. If you
> haven't, the short version is that the name can be t
All,
You may have seen the recent discussions both inside and outside the ASF
about the user of "master" as the name of the default git branch. If you
haven't, the short version is that the name can be traced back to
master/slave and its associations with human slavery.
I'd like
This is an automated email from the ASF dual-hosted git repository.
mturk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-connectors.git
The following commit(s) were added to refs/heads/master by this push:
new 0ff7479 Drop all that beta,rc
hristopherschultz.net>
> >> <mailto:ch...@christopherschultz.net
> > <mailto:ch...@christopherschultz.net>>> wrote:
> >
> >> All,
> >
> >> I tried again to commit to tc10 branch, got commit id
> >> 8dddc11512fbd3b91ed9d737a42e4b8415458
ltz.net>
> >> <mailto:ch...@christopherschultz.net
> > <mailto:ch...@christopherschultz.net>>> wrote:
> >
> >> All,
> >
> >> I tried again to commit to tc10 branch, got commit id
> >> 8dddc11512fbd3b91ed9d737a42e4b8415458ddf.
t;> On Tue, Apr 28, 2020 at 12:21 AM Christopher Schultz
>> > <mailto:ch...@christopherschultz.net>
>> <mailto:ch...@christopherschultz.net
> <mailto:ch...@christopherschultz.net>>> wrote:
>
>> All,
>
>> I tried again to commit to tc10 branch,
pher Schultz
> > > <mailto:ch...@christopherschultz.net>>
> wrote:
> >
> > All,
> >
> > I tried again to commit to tc10 branch, got commit id
> > 8dddc11512fbd3b91ed9d737a42e4b8415458ddf.
> >
> > Moving to tc9 branch:
> >
> > $ git cherry-pick -
tc10 branch, got commit id
> 8dddc11512fbd3b91ed9d737a42e4b8415458ddf.
>
> Moving to tc9 branch:
>
> $ git cherry-pick -n 8dddc11512fbd3b91ed9d737a42e4b8415458ddf
> fatal: bad object 8dddc11512fbd3b91ed9d737a42e4b8415458ddf
>
> - From tc10:
>
> $ git remote -v origin https://github.com/apache/tomcat
On Tue, Apr 28, 2020 at 12:21 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> All,
>
> I tried again to commit to tc10 branch, got commit id
> 8dddc11512fbd3b91ed9d737a42e4b8415458ddf.
>
> Movin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I tried again to commit to tc10 branch, got commit id
8dddc11512fbd3b91ed9d737a42e4b8415458ddf.
Moving to tc9 branch:
$ git cherry-pick -n 8dddc11512fbd3b91ed9d737a42e4b8415458ddf
fatal: bad object 8dddc11512fbd3b91ed9d737a42e4b8415458ddf
. The commit went through
github, merged a PR from a contributor into master. I'm trying to
cherry-pick it back into the 9.0.x branch:
$ git cherry-pick f124a9c7230227d3eaff9d2dc1c52f82ce10e03f error:
commit f124a9c7230227d3eaff9d2dc1c52f82ce10e03f is a merge but no
-m option was given. fatal: cherry
it went through
>> github, merged a PR from a contributor into master. I'm trying to
>> cherry-pick it back into the 9.0.x branch:
>>
>> $ git cherry-pick f124a9c7230227d3eaff9d2dc1c52f82ce10e03f error:
>> commit f124a9c7230227d3eaff9d2dc1c52f82ce10e03f is a
Am 2020-02-24 um 17:33 schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm trying to cherry-pick a commit. The commit went through github,
merged a PR from a contributor into master. I'm trying to cherry-pick
it back into the 9.0.x branch:
$ git cherry-pick
ub.com/apache/tomcat/commit/f124a9c7230227d3eaff9d2dc1c52f82ce10e03f
says: "2 parents 03b2af7 + bf2447b"
I guess that you want this commit:
https://github.com/apache/tomcat/commit/bf2447b4bd9edda25e00c7aaab9fcce455c43f2f
I am not fluent with command-line for this command, as I usually do it
via GUI (provided by
Le 24/02/2020 à 17:33, Christopher Schultz a écrit :
> Any ideas?
I guess you are cherry picking the merge commit, instead of the actual
commit(s) from the PR branch.
Emmanuel Bourg
-
To unsubscribe, e-mail:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I'm trying to cherry-pick a commit. The commit went through github,
merged a PR from a contributor into master. I'm trying to cherry-pick
it back into the 9.0.x branch:
$ git cherry-pick f124a9c7230227d3eaff9d2dc1c52f82ce10e03f
error: commit
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-connectors.git
commit fd76777a421c18608f069432563db4ea71b45a8b
Author: Mark Thomas
AuthorDate: Wed Feb 19 11:40:26 2020 +
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-connectors.git
commit 637edee00ca30b1d927f41d40748809c61ccb70e
Author: Mark Thomas
AuthorDate: Wed Feb 19 11:59:42 2020 +
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-connectors.git
commit a8a7db6ce26c5d64fe974b9c8bb08681f6381313
Author: Mark Thomas
AuthorDate: Mon Feb 17 15:59:02 2020 +
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-connectors.git
The following commit(s) were added to refs/heads/master by this push:
new fb5cce8 First pass at doc updates
This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat-native.git
The following commit(s) were added to refs/heads/master by this push:
new 66c8296 Replace usage of 'svn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 12/7/19 16:29, Mark Thomas wrote:
> On 07/12/2019 21:28, ma...@apache.org wrote:
>> This is an automated email from the ASF dual-hosted git
>> repository.
>>
>> markt pushed a commit to branch 8
On 07/12/2019 21:28, ma...@apache.org wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> markt pushed a commit to branch 8.5.x
> in repository https://gitbox.apache.org/repos/asf/tomcat.git
>
>
> The following commit(s) were added to refs/hea
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new 18de249 Git typo
18de249 is described below
in private branches directly in
the official Tomcat repository, as an alternative to using forks and pull
requests.
Should private branches be allowed in the official Tomcat git repository ?
[ ] Yes
[ ] No
Here is a recap of the voting.
For the binding votes, we have:
Yes: michaelo, ebourg
anches directly in
> the official Tomcat repository, as an alternative to using forks and pull
> requests.
>
> Should private branches be allowed in the official Tomcat git repository ?
> [ ] Yes
> [ ] No
>
Here is a recap of the voting.
For the binding votes, we have:
Yes: michaelo
ly in the official Tomcat repository, as an alternative to using
> forks and pull requests.
>
> Should private branches be allowed in the official Tomcat git repository ?
> [ ] Yes
> [X] No
Mark
-
To
in private branches directly in the official
Tomcat repository, as an alternative to using forks and pull requests.
Should private branches be allowed in the official Tomcat git repository ?
[x] Yes
[ ] No
Certainly Yes. We must be able to conduct our business without relying
on GitHub and without
orks
> and pull
> > requests.
> >
> > Should private branches be allowed in the official Tomcat git
> repository ?
> > [ ] Yes
> > [ ] No
>
> I don't like the term 'private' because everytihing I add to the
> canonical repo
es that are approved by the community such as 8.5.x
> and 7.0.x. It is possible to do development in private branches directly in
> the official Tomcat repository, as an alternative to using forks and pull
> requests.
> >
> > Should private branches be allowed in the official Tomcat git rep
nity such as 8.5.x
> and 7.0.x. It is possible to do development in private branches directly in
> the official Tomcat repository, as an alternative to using forks and pull
> requests.
> >
> > Should private branches be allowed in the official Tomcat git repository
> ?
> > [x] Yes
branches directly in
> the official Tomcat repository, as an alternative to using forks and pull
> requests.
>
> Should private branches be allowed in the official Tomcat git repository ?
> [x] Yes
> [ ] No
Certainly Yes. We must be able to conduct our business without relying
on GitHub and
repository, as an alternative to using
forks and pull requests.
Should private branches be allowed in the official Tomcat git repository ?
[ ] Yes
[X] No
Regards,
Rainer
-
To unsubscribe, e-mail: dev-unsubscr
the official Tomcat repository, as an alternative
> > to using forks and pull requests.
>
> > Should private branches be allowed in the official Tomcat git repository
> ?
> [ ] Yes
> [x] No
>
> I’m not a committer, so my vote doesn’t really count, but I am a long-time
&
the official Tomcat repository, as an alternative
> to using forks and pull requests.
> Should private branches be allowed in the official Tomcat git repository ?
[ ] Yes
[x] No
I’m not a committer, so my vote doesn’t really count, but I am a long-time
Tomcat user and occasional contributer (l
do development
> in private branches directly in the official Tomcat repository, as
> an alternative to using forks and pull requests.
>
> Should private branches be allowed in the official Tomcat git
> repository ? [ ] Yes [X] No
I don't think it makes any sense to have non-stand
Le 11/10/2019 à 16:20, Rémy Maucherat a écrit :
> Should private branches be allowed in the official Tomcat git repository ?
> [X] Yes
> [ ] No
+1
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.a
ternative to using forks and pull
> requests.
>
> Should private branches be allowed in the official Tomcat git repository ?
> [ ] Yes
> [X] No
In my opinion, I think the branches in Tomcat repo should correspond to the
current major maintenance version. Because this can be easily manag
ch as
> 8.5.x
> > and 7.0.x. It is possible to do development in private branches directly
> in
> > the official Tomcat repository, as an alternative to using forks and pull
> > requests.
> >
> > Should private branches be allowed in the official Tomcat git repository
> ?
anches directly in
> the official Tomcat repository, as an alternative to using forks and pull
> requests.
>
> Should private branches be allowed in the official Tomcat git repository ?
> [ ] Yes
> [X] No
>
> I found branches created a disproportionate amount of email traffic which
is
repository, as an alternative to using forks and pull
requests.
Should private branches be allowed in the official Tomcat git repository ?
[ ] Yes
[ ] No
I don't like the term 'private' because everytihing I add to the
canonical repo is intended to merged into upstream sooner or later.
Purely
requests.
Should private branches be allowed in the official Tomcat git repository ?
[ ] Yes
[ ] No
Rémy
activity on these over the last year or so so there has
>>> been no reason to migrate the project to Git.
>>>
>>> I've recently fixed a mod_jk bug and I have a patch ready to fix a
>>> second. These seems like a good time to migrate Tomcat Connectors to
>>> git
Am 08.10.2019 um 13:39 schrieb Rainer Jung:
Am 08.10.2019 um 13:09 schrieb Mark Thomas:
Hi all,
Tomcat Connectors (mod_jk, isapi_redirect) are currently in svn. There
hasn't been much activity on these over the last year or so so there has
been no reason to migrate the project to Git.
I've
Am 08.10.2019 um 13:09 schrieb Mark Thomas:
Hi all,
Tomcat Connectors (mod_jk, isapi_redirect) are currently in svn. There
hasn't been much activity on these over the last year or so so there has
been no reason to migrate the project to Git.
I've recently fixed a mod_jk bug and I have a patch
Hi all,
Tomcat Connectors (mod_jk, isapi_redirect) are currently in svn. There
hasn't been much activity on these over the last year or so so there has
been no reason to migrate the project to Git.
I've recently fixed a mod_jk bug and I have a patch ready to fix a
second. These seems like a good
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/7.0.x by this push:
new 4c5f5bb Back-port svn->git updates
4c5f
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new 13f4296 back-port svn->git updates
13f4
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit 229c6bf6ab37df7bb3bb98a8a6e36b24cbbc062b
Author: Mark Thomas
AuthorDate: Thu Aug 15 20:40:07 2019 +0100
Update
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit d206509dabe5ea9f40aae1f0448716fd42470456
Author: Mark Thomas
AuthorDate: Thu Aug 15 21:01:20 2019 +0100
Update
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new abe9d37 Update source code links to point to Git
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push:
new 42971a3 Update source code links to point
This is an automated email from the ASF dual-hosted git repository.
violetagg pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit cd4cdca0ff68674a4d1af12a944705f6dc285596
Author: Jeremy Boynes
AuthorDate: Sun Jan 26 21:23:55 2014 +0200
add
Mark,
On 7/9/2019 1:45 AM, Mark Thomas wrote:
On 09/07/2019 05:29, Igal Sapir wrote:
Can we move the Tomcat site to Git?
Yes. ASF infra supports both svnpubsub and gitpubsub for websites. There
will need to be a little co-ordination with infra as we'd need to switch
where the source
1 - 100 of 407 matches
Mail list logo
