avermeer commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691832194
> I think you are good to go.
Done, and I see that https://storm.apache.org/contribute/People.html is now
up to date.
Many thanks for the help!
--
This is an automated mes
avermeer merged PR #45:
URL: https://github.com/apache/storm-site/pull/45
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@storm.apache.o
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691822753
I think you are good to go.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific commen
avermeer commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691812398
I have git pushed the changes from `bundle exec jekyll build -d content`,
can I merge this pull request, or should I wait 2/3 days to leave others time
to comment?
--
This is an automa
bipinprasad merged PR #3569:
URL: https://github.com/apache/storm/pull/3569
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@storm.apache
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691776984
> I must confess all this stuff for making minor changes to storm-site seems
to me like a gas factory. I have the feeling that using LaTeX for Storm
documentation would have been even simpler
avermeer commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691769956
> Another idea would be to use the ASF Jenkins CI to build from a different
branch and automatically push the content changes to `asf-site`. So we only
need to deal with the `.md` files a
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691718993
Another idea would be to use the ASF Jenkins CI to build from a different
branch and automatically push the content changes to `asf-site`. So we only
need to deal with the `.md` files and the
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691635335
I think you could manually create a "hardlink" in Windows (don't using
Windows for a few years now).
+1 for adding some warning.
--
This is an automated message from the Apache Git S
avermeer commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691596996
> Looks like the symlink to current is missing :-)
Okay so I think have understood the reason for my mistake: I tried to use
Windows operating system to work on this change on storm
10 matches
Mail list logo
