Am 15.06.23 um 19:07 schrieb Marcus:
Am 15.06.23 um 10:36 schrieb Pedro Lino:
On 06/15/2023 9:30 AM WEST Matthias Seidel
wrote:
Thanks to Peter our Linux buildbots are functional again.
Thanks Peter!
But the buildbot configuration is still on SVN.
I would prefer it on Git. Opinions
On Thu, Jun 15, 2023 at 8:30 AM Matthias Seidel
wrote:
> Hi All,
>
> bumping this up again.
>
> Thanks to Peter our Linux buildbots are functional again.
>
> But the buildbot configuration is still on SVN.
>
> I would prefer it on Git. Opinions?
>
> Regards,
&g
Am 15.06.23 um 10:36 schrieb Pedro Lino:
On 06/15/2023 9:30 AM WEST Matthias Seidel wrote:
Thanks to Peter our Linux buildbots are functional again.
Thanks Peter!
But the buildbot configuration is still on SVN.
I would prefer it on Git. Opinions?
+1
Yes, that would make sense
Hi Matthias, all
> On 06/15/2023 9:30 AM WEST Matthias Seidel wrote:
> Thanks to Peter our Linux buildbots are functional again.
Thanks Peter!
> But the buildbot configuration is still on SVN.
>
> I would prefer it on Git. Opinions?
+1
Yes, that would make sens
Hi All,
bumping this up again.
Thanks to Peter our Linux buildbots are functional again.
But the buildbot configuration is still on SVN.
I would prefer it on Git. Opinions?
Regards,
Matthias
Am 26.11.21 um 15:31 schrieb Matthias Seidel:
> Hi Pedro, all,
>
> I am working with Gav
Hi Bidouille,
Am 29.04.23 um 10:17 schrieb Marcus:
> Am 28.04.23 um 08:20 schrieb Bidouille:
>> Do we have an svn archive somewhere?
>> https://www.openoffice.org/tools/svn_checkout.html
SVN was synchronised with Git. So every commit in SVN should be found in
the Git repo.
What
Am 28.04.23 um 08:20 schrieb Bidouille:
Do we have an svn archive somewhere?
https://www.openoffice.org/tools/svn_checkout.html
have you checked that this is still working? At least I've no access:
"Server not found&
Hello,
Do we have an svn archive somewhere?
https://www.openoffice.org/tools/svn_checkout.html
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Nevermind, Microsoft just published my submission.
Let's call it luck!
Matthias
Am 05.05.22 um 14:42 schrieb Matthias Seidel:
> Really?!
>
> This breaks every download from the Microsoft Store now until the new
> submission is published...
>
> This is clearly documented in the Release Schedule!
Really?!
This breaks every download from the Microsoft Store now until the new
submission is published...
This is clearly documented in the Release Schedule! Please revert.
Matthias
Am 05.05.22 um 14:29 schrieb j...@apache.org:
> Author: jim
> Date: Thu May 5 12:29:49 2022
> New Revision: 5428
Hi Pedro, all,
I am working with Gavin on the Windows buildbot now.
When configuration is finished, Gavin will move the file to Git.
Regards,
Matthias
Am 22.11.21 um 23:04 schrieb Pedro Lino:
> Hi Matthias
>
> I would say silence is agreement.
>
> I assumed AOO moved from SV
I think Git where ever possible.
Best regards,
Carl
On 11/22/21 5:04 PM, Pedro Lino wrote:
Hi Matthias
I would say silence is agreement.
I assumed AOO moved from SVN to GIT, so in my mind it is the only logical
option?
If no one has opposed in 4 days (72 hours), I believe this should be a
Hi Matthias
I would say silence is agreement.
I assumed AOO moved from SVN to GIT, so in my mind it is the only logical
option?
If no one has opposed in 4 days (72 hours), I believe this should be a green
light for Gavin to move on?
Regards,
Pedro
> On 11/22/2021 8:53 PM Matthias Sei
>
>>> With the new Buildbot 3.x we are using, we also added the ability to host
>>> project config files from either an SVN [1] location or GIT [2] . So now
>>> you have a choice. Currently your modified openoffice.py config lives in
>>> SVN, but I can easily mo
Hi ,
On Wed, Nov 17, 2021 at 9:42 PM Matthias Seidel
wrote:
> Hi Gavin
>
> Am 17.11.21 um 11:30 schrieb Gavin McDonald:
> > Hi All,
> >
> > With the new Buildbot 3.x we are using, we also added the ability to host
> > project config files from either an SVN
Hi Gavin
Am 17.11.21 um 11:30 schrieb Gavin McDonald:
> Hi All,
>
> With the new Buildbot 3.x we are using, we also added the ability to host
> project config files from either an SVN [1] location or GIT [2] . So now
> you have a choice. Currently your modified openoffice.py config
Hi All,
With the new Buildbot 3.x we are using, we also added the ability to host
project config files from either an SVN [1] location or GIT [2] . So now
you have a choice. Currently your modified openoffice.py config lives in
SVN, but I can easily move it to GIT - the choice is yours!
HTH
[1
Ah, I see they are "branded" as "Test Development Builds"... ;-)
Just installed it on macOS Catalina with the latest AdoptOpenJDK 11.
Am 06.08.21 um 22:16 schrieb Jim Jagielski:
> I am uploading both the regular and the ./Dev/ builds... just in case there
> is something in the Dev builds themsel
I am uploading both the regular and the ./Dev/ builds... just in case there is
something in the Dev builds themselves which causes issues
> On Aug 6, 2021, at 3:44 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Sorry, these are NOT Dev builds, compare to Dev2:
>
> https://dist.apache.org/repos
Hi Jim,
Sorry, these are NOT Dev builds, compare to Dev2:
https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev2/binaries/en-US/
Regards,
Matthias
Am 06.08.21 um 21:36 schrieb j...@apache.org:
> Author: jim
> Date: Fri Aug 6 19:36:48 2021
> New Revision: 49231
>
> Log:
> AOO 4.2.0-De
Hello all,
On Thu, Jun 17, 2021 at 02:54:26AM +0200, Damjan Jovanovic wrote:
> On Thu, Jun 17, 2021 at 1:34 AM Don Lewis wrote:
>
> > On 16 Jun, ard...@apache.org wrote:
> > > Author: ardovm
> > > Date: Wed Jun 16 19:07:44 2021
> > > New Revision: 1890844
> > >
> > > URL: http://svn.apache.org/
On Thu, Jun 17, 2021 at 1:34 AM Don Lewis wrote:
> On 16 Jun, ard...@apache.org wrote:
> > Author: ardovm
> > Date: Wed Jun 16 19:07:44 2021
> > New Revision: 1890844
> >
> > URL: http://svn.apache.org/viewvc?rev=1890844&view=rev
> > Log:
> > Build script for AOO 4.1.10 under Mingw
> >
> > Better
On 16 Jun, ard...@apache.org wrote:
> Author: ardovm
> Date: Wed Jun 16 19:07:44 2021
> New Revision: 1890844
>
> URL: http://svn.apache.org/viewvc?rev=1890844&view=rev
> Log:
> Build script for AOO 4.1.10 under Mingw
>
> Better late than never... could be used as a template for the future
I tho
the same used for
> release builds.
>
> I must confess I got lost a couple of times while searching the wiki
> for this information, but I eventually found out this SVN repository:
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>
> I would like to propose som
e builds.
>
> I must confess I got lost a couple of times while searching the wiki
> for this information, but I eventually found out this SVN repository:
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>
> I would like to propose some changes to those scripts. They d
Dear List,
while working on pull requests, I was wondering how to test the most
common build options for OpenOffice -- possibly the same used for
release builds.
I must confess I got lost a couple of times while searching the wiki
for this information, but I eventually found out this SVN
Hi -
I’m about to pull the trigger on completing the CMS migration.
Are you planning on making changes on GitHub too?
Regards,
Dave
Sent from my iPhone
> On Nov 18, 2020, at 8:09 AM, msei...@apache.org wrote:
>
> Author: mseidel
> Date: Wed Nov 18 16:09:05 2020
> New Revision: 1068165
>
> L
Yes, no problem.
Any idea how long it will last until we switch? The layout is not 100%
identical for openoffice.org.
Matthias
Am 14.11.20 um 23:26 schrieb Dave Fisher:
> Would you please make the same changes in the new location.
>
> Sent from my iPhone
>
>> On Nov 14, 2020, at 9:50 AM, msei...
Would you please make the same changes in the new location.
Sent from my iPhone
> On Nov 14, 2020, at 9:50 AM, msei...@apache.org wrote:
>
> Author: mseidel
> Date: Sat Nov 14 17:50:04 2020
> New Revision: 1883427
>
> URL: http://svn.apache.org/viewvc?rev=1883427&view=rev
> Log:
> Use Italian
Hi Aivaras,
/"2020 m. spalio 15 d."/
/Is this right?/
/We released on November 10th.
/
//Regards,//
// Matthias
//
Am 11.11.20 um 15:23 schrieb astepuko...@apache.org:
> Author: astepukonis
> Date: Wed Nov 11 14:23:06 2020
> New Revision: 1883306
>
> URL: http://svn.apache.org/viewvc?rev=18
Hi Dave,
On 10/19/20 4:44 PM, Dave Fisher wrote:
Hi -
I added more analysis in README.txt
New is FRAMEWORKS.txt which has some notes about Pelican, JBake, Hugo, and
Jekyll frameworks.
So, far JBake is the most promising.
If anyone has another framework to consider let me know.
I’ll be taki
Hi -
I added more analysis in README.txt
New is FRAMEWORKS.txt which has some notes about Pelican, JBake, Hugo, and
Jekyll frameworks.
So, far JBake is the most promising.
If anyone has another framework to consider let me know.
I’ll be taking my next steps on Wednesday.
Regards,
Dave
> On
Hi -
After discussing the CMS migration of the OpenOffice.org site on the
anniversary call yesterday with Carl I created a README.txt and ssi.json files
to start the process towards a description that can be easier to fit into
whatever new framework we choose.
The next step will be to look int
Hi Andrea,
Am 15.08.19 um 08:30 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> Shouldn't SVN be read-only now?!
>> This will introduce some inconsistencies to Git now...
>
> If it is writable, please do not fix it!
>
> We definitely need some README there (
Matthias Seidel wrote:
Shouldn't SVN be read-only now?!
This will introduce some inconsistencies to Git now...
If it is writable, please do not fix it!
We definitely need some README there (in trunk) that points to the new
repository URL, and a last commit message for it saying "Po
/asf/openoffice.git
>>
>>
>> The following commit(s) were added to refs/heads/AOO417 by this push:
>> new 4aba5f8 Sync w/ SVN
>> 4aba5f8 is described below
>>
>> commit 4aba5f85ea42f3f097b6465edfd2f848bb5ed4b3
>> Author: Jim Jagielski
>>
sitory https://gitbox.apache.org/repos/asf/openoffice.git
>
>
> The following commit(s) were added to refs/heads/AOO417 by this push:
> new 4aba5f8 Sync w/ SVN
> 4aba5f8 is described below
>
> commit 4aba5f85ea42f3f097b6465edfd2f848bb5ed4b3
> Author: Jim Jagielski
> Aut
Personally, I think migrating from svn to git while in the midst of also trying
to cut a release was somewhat unwise... As far as SVN being read only,
obviously I was able to commit to the AOO417 branch. So I've no idea what the
status is... I was just as surprised, but since my entire
we can
> just update source.mdtext. I've moved your source_new.mdtext to be the
> new version of source.mdtext and we'll continue from there.
>
Sounds good...
This page also references a "Subversion Basics" page --
https://openoffice.apache.org/svn-basics.html
which has a L
Shouldn't SVN be read-only now?!
This will introduce some inconsistencies to Git now...
Matthias
Am 14.08.19 um 17:51 schrieb j...@apache.org:
> Author: jim
> Date: Wed Aug 14 15:51:11 2019
> New Revision: 1865164
>
> URL: http://svn.apache.org/viewvc?rev=1865164&view=r
On 13/08/2019 Kay Schenk wrote:
The page name from the current project website repository is --
source_new.mdtext as you probably saw.
There is no need to be shy here... we have version control and we can
just update source.mdtext. I've moved your source_new.mdtext to be the
new version of so
confusing
for the general public. See
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
where we still have the SVN commands (which WILL work and give you the
frozen SVN trunk, with no indications that this is frozen; it is now
easy to say that we should have added a last SVN
Agreed. Cms is another beast. I think it would be a good idea to sum up the
current discussion on a cwiki page.
Am 14. August 2019 11:21:10 MESZ schrieb Andrea Pescetti :
>On 03/08/2019 Peter Kovacs wrote:
>> I have pushed Infra a bit. We are now migrating. ...
>> Sorry if this moves now a bit u
Hello Andrea,
hello *
Am 14.08.19 um 11:21 schrieb Andrea Pescetti:
> On 03/08/2019 Peter Kovacs wrote:
>> I have pushed Infra a bit. We are now migrating. ...
>> Sorry if this moves now a bit uncoordinated, but I want to get this done.
>
> It's now clear that this was indeed quite rushed, but I
On 03/08/2019 Peter Kovacs wrote:
I have pushed Infra a bit. We are now migrating. ...
Sorry if this moves now a bit uncoordinated, but I want to get this done.
It's now clear that this was indeed quite rushed, but I'm prepared to
working with git too and I'm sure we can fix the missing bits w
I, I was able to add and commit a new page to the project web
>> site
>>> --
>>> https://openoffice.apache.org/
>>>
>>> to verify that svn is still OK there also.
>>>
>>>
>>>
>>> On Tue, Aug 13, 2019 at 2:48 AM Matthia
s able to add and commit a new page to the project web
> site
> > --
> > https://openoffice.apache.org/
> >
> > to verify that svn is still OK there also.
> >
> >
> >
> > On Tue, Aug 13, 2019 at 2:48 AM Matthias Seidel <
> matthias.sei...@h
web site
> --
> https://openoffice.apache.org/
>
> to verify that svn is still OK there also.
>
>
>
> On Tue, Aug 13, 2019 at 2:48 AM Matthias Seidel
> wrote:
>
>> Hi all,
>>
>> Totally forgot to say that I was able to commit to that directory
As an FYI, I was able to add and commit a new page to the project web site
--
https://openoffice.apache.org/
to verify that svn is still OK there also.
On Tue, Aug 13, 2019 at 2:48 AM Matthias Seidel
wrote:
> Hi all,
>
> Totally forgot to say that I was able to commit to that direct
Marcus:
> Am 13.08.19 um 00:28 schrieb Peter Kovacs:
>> Infra Chat Log from on slack ( for documentation reasons):
>>
>> petko 23:44 Uhr
>> Hello, is SVN path
>> https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/
>> readonly? (edited)
>>
>
Am 13.08.19 um 00:28 schrieb Peter Kovacs:
Infra Chat Log from on slack ( for documentation reasons):
petko 23:44 Uhr
Hello, is SVN path
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/
readonly? (edited)
warwalrux 23:54 Uhr
I believe it's readonly to all but members o
Infra Chat Log from on slack ( for documentation reasons):
petko 23:44 Uhr
Hello, is SVN path
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/
readonly? (edited)
warwalrux 23:54 Uhr
I believe it's readonly to all but members of the openoffice group.
(edited)
Gavin McDonald
mmit was
> rejected. Transcript below.
>
> $ svn mkdir aoo417
> A aoo417
> $ svn ci -m "Empty dir for 4.1.7 update feeds."
> Adding aoo417
> svn: E195023: Commit failed:
> svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is
&
Matthias Seidel wrote:
https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
read-only now?
Can anyone confirm?
Confirmed. I tried adding an empty "aoo417" directory and commit was
rejected. Transcript below.
$ svn mkdir aoo417
A aoo417
$ svn ci -m &quo
Infra confirms. I ask now what they need to fix it.
On 13.08.19 00:00, Marcus wrote:
> Am 12.08.19 um 23:39 schrieb Matthias Seidel:
>> https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
>> read-only now?
>>
>> Can anyone confirm?
>
> yes, I cannot send a commit as access is den
Am 12.08.19 um 23:39 schrieb Matthias Seidel:
https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
read-only now?
Can anyone confirm?
yes, I cannot send a commit as access is denied.
Marcus
-
To unsubscribe
Hi all,
https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be
read-only now?
Can anyone confirm?
Regards,
Matthias
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
>
> For the specific guy that told me I didn't speak up.
>
> This is still unresponded...
>
> Matthias
>
> Am 06.08.19 um 11:48 schrieb Matthias Seidel:
>> Hi all,
>>
>> Any progress?
>>
>> Git is active since Saturday.
>> SVN is n
Hi,
For the specific guy that told me I didn't speak up.
This is still unresponded...
Matthias
Am 06.08.19 um 11:48 schrieb Matthias Seidel:
> Hi all,
>
> Any progress?
>
> Git is active since Saturday.
> SVN is now read only (for trunk, branches and tags).
>
>
m:39
>>
>> There we have to change the condition for the "Revision ID"
>>
>> Instead of the condition for the git-svn-id we should take the hash
>> which followed to the word "commit" in the first line.
>>
>> Here is an ouput with git show HEAD f
/SvnRevision.pm:39
>
> There we have to change the condition for the "Revision ID"
>
> Instead of the condition for the git-svn-id we should take the hash
> which followed to the word "commit" in the first line.
>
> Here is an ouput with git show HEAD
re the "git switch" would still take the git-svn-id
and builds after would take the git hash.
>
> Instead of the condition for the git-svn-id we should take the hash
> which followed to the word "commit" in the first line.
>
> Here is an
Hi all,
Any progress?
Git is active since Saturday.
SVN is now read only (for trunk, branches and tags).
New Builds do not contain any revision information.
We have documentation that must be updated asap, e.g.:
https://openoffice.apache.org/source.html
Who wants to write a blog post or post
uot;Peter Kovacs"
>> À: dev@openoffice.apache.org
>> Envoyé: Samedi 3 Août 2019 08:25:25
>> Objet: Re: [resolution] svn migration plan
>>
>>
>> On 03.08.19 08:20, Mechtilde wrote:
>>> Hello,
>>>
>>> Am 03.08.19 um 07:58 schrieb Damj
Hi Mechtilde,
Am 03.08.19 um 13:56 schrieb Mechtilde:
> Hello,
>
> I looked into
>
> main/solenv/bin/modules/SvnRevision.pm:39
>
> There we have to change the condition for the "Revision ID"
>
> Instead of the condition for the git-svn-id we should take
Hello,
I looked into
main/solenv/bin/modules/SvnRevision.pm:39
There we have to change the condition for the "Revision ID"
Instead of the condition for the git-svn-id we should take the hash
which followed to the word "commit" in the first line.
Here is an ouput with git
I have ask infra on slack to look into it. I hope they give feedback what the
issue is.
I have no update on this so far.
Am 3. August 2019 12:08:20 MESZ schrieb Mechtilde :
>Hello,
>
>is it now possible :
>
>1.) to get a recent buildbot maschine for the Linux Builds
> like https://issues.apach
Hello,
is it now possible :
1.) to get a recent buildbot maschine for the Linux Builds
like https://issues.apache.org/jira/browse/INFRA-17822
2.) to configure the connection to the new Git-Reo
3.) to give the rights to configure the buildbot to member of the PMC
who want to do it
Kind regar
Hello
Am 03.08.19 um 07:47 schrieb Peter Kovacs:
> Hello all,
>
> I have pushed Infra a bit. We are now migrating.
>
> So migration will be finished soon.
>
After finishing the migration the SVN repository is frozen.
All commits are only visible under
https://github.com
Do you have published announcement on AOO blog?
That will be fine.
- Mail original -
> De: "Peter Kovacs"
> À: dev@openoffice.apache.org
> Envoyé: Samedi 3 Août 2019 08:25:25
> Objet: Re: [resolution] svn migration plan
>
>
> On 03.08.19 08:20, Mechtil
Am 03.08.19 um 10:16 schrieb Peter Kovacs:
> I have not managed to find the information to change in our source CMS
> webside.
>
> If you link your github account here with Apache, then you get write
> access on github directly:
>
> https://gitbox.apache.org/setup/
I'm trying to folloe the ins
I have not managed to find the information to change in our source CMS
webside.
If you link your github account here with Apache, then you get write
access on github directly:
https://gitbox.apache.org/setup/
All the Best
Peter
On 03.08.19 08:25, Peter Kovacs wrote:
> On 03.08.19 08:20, Mecht
On 03.08.19 08:20, Mechtilde wrote:
> Hello,
>
> Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
>> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs wrote:
>>> I suggest we use the short hash.
>>>
>>>
>> For what? Why can't we "git tag" relevant commits and use the tag instead?
> I think we should hav
Hello,
Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs wrote:
>
>> Hello all,
>>
>> I have pushed Infra a bit. We are now migrating.
>>
>> So migration will be finished soon.
>>
>>
> Excellent :).
>
>
>>
>> I suggest we use the short hash.
>>
>>
> F
On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs wrote:
> Hello all,
>
> I have pushed Infra a bit. We are now migrating.
>
> So migration will be finished soon.
>
>
Excellent :).
>
> I suggest we use the short hash.
>
>
For what? Why can't we "git tag" relevant commits and use the tag instead?
Dam
, Peter Kovacs wrote:
> On 29.07.19 17:18, Matthias Seidel wrote:
>> Hi Peter,
>>
>> Am 29.07.19 um 00:39 schrieb Peter Kovacs:
>>> A different suggestion we use the git commit count. The command is:
>>>
>>> |git rev-list --all --count It will deliver so
Welcome back George,
yes I have not forgotten your work. I do hope you continue. I am really
happy on your post.
I liked your proposal for the new design. I would really like to see
that they move into our "production".
The only thing is that in my opinion the static side generator does not
fit
code changes ready?
We use the SVN revision in our About dialog, and for creating the
source
builds. This has to be adapted when we switch to git.
Using the git hash (short or long) instead? This should have been
discussed...
Given the lack of response, this has yet to be investigated...
Meanwhi
On 29.07.19 17:18, Matthias Seidel wrote:
> Hi Peter,
>
> Am 29.07.19 um 00:39 schrieb Peter Kovacs:
>> A different suggestion we use the git commit count. The command is:
>>
>> |git rev-list --all --count It will deliver something that looks similar
>> to the s
headers. I did the bulk of the
work in Dec 2011. No real plans to help until after Apachecon.
Please keep the OpenOffice website in SVN until a Git based framework using new
tools is built. Once it is we can do a bulk move which could include html
conversions.
Personally, I kind of like the JBake
Hi Peter,
Am 29.07.19 um 00:39 schrieb Peter Kovacs:
> A different suggestion we use the git commit count. The command is:
>
> |git rev-list --all --count It will deliver something that looks similar
> to the svn number we already use. All the Best Peter |
How would such a simple co
Hi Gavin
Sounds like a load of work, Especially for the Templates. Does Pelican
serve HTML and markdown mixed?
Regards Raphael.
On Mon, Jul 29, 2019 at 10:48 AM Gavin McDonald wrote:
>
> Hi all,
>
> On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote:
> >
> > Hello Peter,
> >
> > I have propo
Hi all,
On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote:
>
> Hello Peter,
>
> I have proposed some time ago the move to a static site generator — like
Jekyll, Hugo etc. —
> as I was redesigning OpenOffice’s front-page. That would greatly help
reduce tech diversity
> and maintenance as only s
Hello Peter,
I have proposed some time ago the move to a static site generator — like
Jekyll, Hugo etc. —
as I was redesigning OpenOffice’s front-page. That would greatly help reduce
tech diversity
and maintenance as only static html files will be served.
Most static site generators work with
On 28.07.19 23:10, Marcus wrote:
> Am 28.07.19 um 21:31 schrieb Peter Kovacs:
>> Cms will be shut down soon. The question is how we deal with this.
>> Info is in the chat protocol in my original post.
>
> OK, then we will have a big problem in order to serve our website pages.
>
> Marcus
>
>
Ther
A different suggestion we use the git commit count. The command is:
|git rev-list --all --count It will deliver something that looks similar
to the svn number we already use. All the Best Peter |
On 29.07.19 00:17, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 28.07.19 um 23:12 schri
t;>>> tags are moved. All other folders should remain as is.
>>>>>>
>>>>>> I hope this suits everyone.
>>>>> Do we have the necessary code changes ready?
>>>>>
>>>>> We use the SVN revision in our About dia
read my mail until the end...
I have created the request. Simply requesting that trunc, branch and
tags are moved. All other folders should remain as is.
I hope this suits everyone.
Do we have the necessary code changes ready?
We use the SVN revision in our About dialog, and for creating the
s
Am 28.07.19 um 21:31 schrieb Peter Kovacs:
Cms will be shut down soon. The question is how we deal with this.
Info is in the chat protocol in my original post.
OK, then we will have a big problem in order to serve our website pages.
Marcus
tial discussion.
>>>> Obviously you didn't read my mail until the end...
>>>>> I have created the request. Simply requesting that trunc, branch
>and
>>>>> tags are moved. All other folders should remain as is.
>>>>>
>>>>>
> Obviously you didn't read my mail until the end...
>>>> I have created the request. Simply requesting that trunc, branch and
>>>> tags are moved. All other folders should remain as is.
>>>>
>>>> I hope this suits everyone.
>>> Do we ha
trunc, branch and
tags are moved. All other folders should remain as is.
I hope this suits everyone.
Do we have the necessary code changes ready?
We use the SVN revision in our About dialog, and for creating the source
builds. This has to be adapted when we switch to git.
Using the git hash (sho
ch and
>> tags are moved. All other folders should remain as is.
>>
>> I hope this suits everyone.
> Do we have the necessary code changes ready?
>
> We use the SVN revision in our About dialog, and for creating the source
> builds. This has to be adapted when we switch
> I hope this suits everyone.
Do we have the necessary code changes ready?
We use the SVN revision in our About dialog, and for creating the source
builds. This has to be adapted when we switch to git.
Using the git hash (short or long) instead? This should have been
discussed...
Regards,
M
Hi Peter,
Am 21.07.19 um 12:02 schrieb Peter Kovacs:
> On 21.07.19 11:42, Matthias Seidel wrote:
>>> 4) As a user I want o be aware how the SVN right management is set. We
>>> had issues with this. This was not the decision in favour for git but
>>> for cWiki. And I
:
> Hi brane,
>
> The threads are linked in my first post.
>
> It is for me a workflow thing.
> I need a decentral versioning system instead of a central one.
> And I want github as public patch interface.
> Both do not work with svn.
>
> I add a reason that I heard at
On 21.07.19 11:42, Matthias Seidel wrote:
>
>> 4) As a user I want o be aware how the SVN right management is set. We
>> had issues with this. This was not the decision in favour for git but
>> for cWiki. And I add this now, since I do a use case recap :P
> In fact, it wa
t;
>>> Which particular "decentralised" feature do you miss most? For example,
>>> there's work going on to implement client-side shelving (similar to 'git
>>> stash'), it's experimental but available in various forms in the last 3
>>&g
gt;> there's work going on to implement client-side shelving (similar to 'git
>> stash'), it's experimental but available in various forms in the last 3
>> Subversion (minor) releases
> Most of the missing features were the reason why Git was developed.
> As
miss most? For example,
> > there's work going on to implement client-side shelving (similar to 'git
> > stash'), it's experimental but available in various forms in the last 3
> > Subversion (minor) releases
>
> Most of the missing features were the reason
1 - 100 of 634 matches
Mail list logo
