date:20191030

Re: moving the site from SVN to git

2019-10-30 Thread Jon Haddad

Thanks Michael, that's exactly what I needed.

On Wed, Oct 30, 2019 at 1:44 PM Michael Shuler 
wrote:

> Looks like the source markdown was added in the next commit.
> http://svn.apache.org/viewvc?view=revision=1857226
>
> (which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)
>
> Michael
>
> On 10/30/19 3:29 PM, Nate McCall wrote:
> > Unfortunately my svn foo is about as atrophied as yours. I followed the
> > usual steps when publishing as I've done with the other posts, so no idea
> > what happened? I dont have anything uncommitted locally either.
> >
> > Whatever we can do to get it showing until we move off SVN (or just move)
> > is fine with me.
> >
> > On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:
> >
> >> I figured out what was wrong with the site generation, I've pushed up a
> >> fix.
> >>
> >> I regenerated the site and noticed the blog post for streaming was
> marked
> >> as deleted, which was odd.  I dug back through the history and found it
> an
> >> HTML file committed at
> >> http://svn.apache.org/viewvc?view=revision=1857225, but I'm
> not
> >> sure where the original content is.  (My SVN foo is terrible now)
> >>
> >> Looking at the Git history I see this:
> >>
> >> commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> >> Author: zznate 
> >> Date:   Wed Apr 10 01:16:07 2019 +
> >>
> >>  CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
> >>
> >>  git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> >> 13f79535-47bb-0310-9956-ffa450edef68
> >> <
> http://svn.apache.org/repos/asf/cassandra/site@185722513f79535-47bb-0310-9956-ffa450edef68
> >
> >>
> >> Was this just published directly as HTML?
> >>
> >> Nate, do you remember how this was handled?  Am I missing something
> >> obvious?
> >>
> >> Jon
> >>
> >> On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
> >>
> >>> I'll take a look at the website generation.  Thanks for fixing manually
> >>> for now.
> >>>
> >>> On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler  >
> >>> wrote:
> >>>
>  I have updated the new releases in:
>  src/_data/releases.yaml
> 
>  I ran through the docker build/run, yet the main index and download
>  pages of the site were not modified with the new release versions and
>  dates. I'm going to reset --hard and hand edit those pages. #justFYI
> 
>  Michael
> 
>  On 10/17/19 9:07 AM, Jon Haddad wrote:
> > The migration is finished.
> >
> > I had to fix a few things along the way.  The docker containers
> didn't
> > build correctly (based on debian:latest rather than a fixed tag), and
>  the
> > site had to be served out of the content directory rather than the
>  publish
> > one we were using.
> >
> > I'm going to address a couple things as follow ups.  We still point
>  people
> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> >> Hugo,
> > which will make the entire process a lot easier.
> >
> > Jon
> >
> >
> >
> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad 
> wrote:
> >
> >> OK, I checked with INFRA on some details and will finish the
> >> migration
> >> tomorrow.
> >>
> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> >> wrote:
> >>
> >>> Awesome, thanks Michael.
> >>>
> >>> We need to do a little bit of additional configuration to have it
>  switch
> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
>  the
> >>> servers how the site should be published.  I can take care of it
> >>> tomorrow.
> >>>
> >>> Reference:
> >>>
> 
> >>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> >>>
> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
>  mich...@pbandjelly.org>
> >>> wrote:
> >>>
>  committed! :)
> 
>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> 
>  Michael
> 
>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> > I think we can safely ignore them.  Thanks for figuring this out.
> >
> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
>  mich...@pbandjelly.org
> >
> > wrote:
> >
> >> I'm making progress through many periodic timeouts to svn.a.o
> and
> >> restarts, but it appears that svn2git is smart enough to pick up
>  where
> >> it left off. The first commit captured at the svn path I'm
>  specifying
>  is
> >> when Cassandra was moved to a top level project at r922689
>  (2010-03-13).
> >> I don't know the old incubator path, and it's probably OK to
> >> ignore
>  the
> >> few older incubator commits? I imagine it would mean starting
> >> over
>  the
> >> entire import to pull

Re: moving the site from SVN to git

2019-10-30 Thread Michael Shuler


Looks like the source markdown was added in the next commit.
http://svn.apache.org/viewvc?view=revision=1857226

(which I see in git as commit 157df5cdfb83cb2edd0051002736316f5f470ad9)

Michael

On 10/30/19 3:29 PM, Nate McCall wrote:

Unfortunately my svn foo is about as atrophied as yours. I followed the
usual steps when publishing as I've done with the other posts, so no idea
what happened? I dont have anything uncommitted locally either.

Whatever we can do to get it showing until we move off SVN (or just move)
is fine with me.

On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:


I figured out what was wrong with the site generation, I've pushed up a
fix.

I regenerated the site and noticed the blog post for streaming was marked
as deleted, which was odd.  I dug back through the history and found it an
HTML file committed at
http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
sure where the original content is.  (My SVN foo is terrible now)

Looking at the Git history I see this:

commit f00523b1eefc90b5e4515db0d8c3ab207656684b
Author: zznate 
Date:   Wed Apr 10 01:16:07 2019 +

 CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti

 git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
13f79535-47bb-0310-9956-ffa450edef68


Was this just published directly as HTML?

Nate, do you remember how this was handled?  Am I missing something
obvious?

Jon

On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:


I'll take a look at the website generation.  Thanks for fixing manually
for now.

On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
wrote:


I have updated the new releases in:
src/_data/releases.yaml

I ran through the docker build/run, yet the main index and download
pages of the site were not modified with the new release versions and
dates. I'm going to reset --hard and hand edit those pages. #justFYI

Michael

On 10/17/19 9:07 AM, Jon Haddad wrote:

The migration is finished.

I had to fix a few things along the way.  The docker containers didn't
build correctly (based on debian:latest rather than a fixed tag), and

the

site had to be served out of the content directory rather than the

publish

one we were using.

I'm going to address a couple things as follow ups.  We still point

people

to IRC, I'll update that to slack.  Longer term I'll migrate it to

Hugo,

which will make the entire process a lot easier.

Jon



On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:


OK, I checked with INFRA on some details and will finish the

migration

tomorrow.

On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 

wrote:



Awesome, thanks Michael.

We need to do a little bit of additional configuration to have it

switch

over.  Specifically, we need to set up the .asf.yaml config to tell

the

servers how the site should be published.  I can take care of it
tomorrow.

Reference:




https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite


On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


committed! :)

https://gitbox.apache.org/repos/asf?p=cassandra-website.git

Michael

On 10/3/19 12:22 PM, Jon Haddad wrote:

I think we can safely ignore them.  Thanks for figuring this out.

On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <

mich...@pbandjelly.org


wrote:


I'm making progress through many periodic timeouts to svn.a.o and
restarts, but it appears that svn2git is smart enough to pick up

where

it left off. The first commit captured at the svn path I'm

specifying

is

when Cassandra was moved to a top level project at r922689

(2010-03-13).

I don't know the old incubator path, and it's probably OK to

ignore

the

few older incubator commits? I imagine it would mean starting

over

the

entire import to pull in those older incubator svn commits, then
changing the url and somehow importing the newer path on top?

I tried using a local path as the source to try to speed things

up,

after I got my first few timeouts, but that fails.

Curious if anyone really cares if we lose a few early commits -

if

so, I

can try to figure out the old path and start again.

Michael

On 10/3/19 11:14 AM, Jon Haddad wrote:

Thanks for taking a look, Michael.  Hopefully you have better

luck

than

me

:)

On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <

mich...@pbandjelly.org>

wrote:


I cloned the empty cassandra-website git repo, and I'm running:

svn2git http://svn.apache.org/repos/asf/cassandra/site

--rootistrunk

--no-minimize-url

..to see what I get. An svn checkout of the above url says it's

only

69M, so I suppose it's pulling all history of all time for all

projects?


I'll let this roll for a while I run an errand and report back!

Michael

On 10/2/19 9:30 PM, Jon Haddad wrote:

Daniel referred me to the GitBox self service

Re: moving the site from SVN to git

2019-10-30 Thread Jon Haddad

I think I figured out what happened.. it's regenerating into a different
directory than originally was.  I'll dig into why.

The site's already moved and publishing via git, I'm just trying to figure
out the last couple wrinkles that I didn't spot in the process.

On Wed, Oct 30, 2019 at 1:30 PM Nate McCall  wrote:

> Unfortunately my svn foo is about as atrophied as yours. I followed the
> usual steps when publishing as I've done with the other posts, so no idea
> what happened? I dont have anything uncommitted locally either.
>
> Whatever we can do to get it showing until we move off SVN (or just move)
> is fine with me.
>
> On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:
>
> > I figured out what was wrong with the site generation, I've pushed up a
> > fix.
> >
> > I regenerated the site and noticed the blog post for streaming was marked
> > as deleted, which was odd.  I dug back through the history and found it
> an
> > HTML file committed at
> > http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
> > sure where the original content is.  (My SVN foo is terrible now)
> >
> > Looking at the Git history I see this:
> >
> > commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> > Author: zznate 
> > Date:   Wed Apr 10 01:16:07 2019 +
> >
> > CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
> >
> > git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> > 13f79535-47bb-0310-9956-ffa450edef68
> > <
> http://svn.apache.org/repos/asf/cassandra/site@185722513f79535-47bb-0310-9956-ffa450edef68
> >
> >
> > Was this just published directly as HTML?
> >
> > Nate, do you remember how this was handled?  Am I missing something
> > obvious?
> >
> > Jon
> >
> > On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
> >
> > > I'll take a look at the website generation.  Thanks for fixing manually
> > > for now.
> > >
> > > On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler  >
> > > wrote:
> > >
> > >> I have updated the new releases in:
> > >>src/_data/releases.yaml
> > >>
> > >> I ran through the docker build/run, yet the main index and download
> > >> pages of the site were not modified with the new release versions and
> > >> dates. I'm going to reset --hard and hand edit those pages. #justFYI
> > >>
> > >> Michael
> > >>
> > >> On 10/17/19 9:07 AM, Jon Haddad wrote:
> > >> > The migration is finished.
> > >> >
> > >> > I had to fix a few things along the way.  The docker containers
> didn't
> > >> > build correctly (based on debian:latest rather than a fixed tag),
> and
> > >> the
> > >> > site had to be served out of the content directory rather than the
> > >> publish
> > >> > one we were using.
> > >> >
> > >> > I'm going to address a couple things as follow ups.  We still point
> > >> people
> > >> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> > Hugo,
> > >> > which will make the entire process a lot easier.
> > >> >
> > >> > Jon
> > >> >
> > >> >
> > >> >
> > >> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad 
> wrote:
> > >> >
> > >> >> OK, I checked with INFRA on some details and will finish the
> > migration
> > >> >> tomorrow.
> > >> >>
> > >> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> > wrote:
> > >> >>
> > >> >>> Awesome, thanks Michael.
> > >> >>>
> > >> >>> We need to do a little bit of additional configuration to have it
> > >> switch
> > >> >>> over.  Specifically, we need to set up the .asf.yaml config to
> tell
> > >> the
> > >> >>> servers how the site should be published.  I can take care of it
> > >> >>> tomorrow.
> > >> >>>
> > >> >>> Reference:
> > >> >>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> > >> >>>
> > >> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
> > >> mich...@pbandjelly.org>
> > >> >>> wrote:
> > >> >>>
> > >>  committed! :)
> > >> 
> > >>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> > >> 
> > >>  Michael
> > >> 
> > >>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> > >> > I think we can safely ignore them.  Thanks for figuring this
> out.
> > >> >
> > >> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
> > >> mich...@pbandjelly.org
> > >> >
> > >> > wrote:
> > >> >
> > >> >> I'm making progress through many periodic timeouts to svn.a.o
> and
> > >> >> restarts, but it appears that svn2git is smart enough to pick
> up
> > >> where
> > >> >> it left off. The first commit captured at the svn path I'm
> > >> specifying
> > >>  is
> > >> >> when Cassandra was moved to a top level project at r922689
> > >>  (2010-03-13).
> > >> >> I don't know the old incubator path, and it's probably OK to
> > ignore
> > >>  the
> > >> >> few older incubator commits? I imagine it would mean starting
> > over
> > >> the
> > >> >> entire import to pull in those older incubator svn

Re: moving the site from SVN to git

2019-10-30 Thread Nate McCall

Unfortunately my svn foo is about as atrophied as yours. I followed the
usual steps when publishing as I've done with the other posts, so no idea
what happened? I dont have anything uncommitted locally either.

Whatever we can do to get it showing until we move off SVN (or just move)
is fine with me.

On Thu, Oct 31, 2019 at 9:17 AM Jon Haddad  wrote:

> I figured out what was wrong with the site generation, I've pushed up a
> fix.
>
> I regenerated the site and noticed the blog post for streaming was marked
> as deleted, which was odd.  I dug back through the history and found it an
> HTML file committed at
> http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
> sure where the original content is.  (My SVN foo is terrible now)
>
> Looking at the Git history I see this:
>
> commit f00523b1eefc90b5e4515db0d8c3ab207656684b
> Author: zznate 
> Date:   Wed Apr 10 01:16:07 2019 +
>
> CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti
>
> git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
> 13f79535-47bb-0310-9956-ffa450edef68
> 
>
> Was this just published directly as HTML?
>
> Nate, do you remember how this was handled?  Am I missing something
> obvious?
>
> Jon
>
> On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:
>
> > I'll take a look at the website generation.  Thanks for fixing manually
> > for now.
> >
> > On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
> > wrote:
> >
> >> I have updated the new releases in:
> >>src/_data/releases.yaml
> >>
> >> I ran through the docker build/run, yet the main index and download
> >> pages of the site were not modified with the new release versions and
> >> dates. I'm going to reset --hard and hand edit those pages. #justFYI
> >>
> >> Michael
> >>
> >> On 10/17/19 9:07 AM, Jon Haddad wrote:
> >> > The migration is finished.
> >> >
> >> > I had to fix a few things along the way.  The docker containers didn't
> >> > build correctly (based on debian:latest rather than a fixed tag), and
> >> the
> >> > site had to be served out of the content directory rather than the
> >> publish
> >> > one we were using.
> >> >
> >> > I'm going to address a couple things as follow ups.  We still point
> >> people
> >> > to IRC, I'll update that to slack.  Longer term I'll migrate it to
> Hugo,
> >> > which will make the entire process a lot easier.
> >> >
> >> > Jon
> >> >
> >> >
> >> >
> >> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:
> >> >
> >> >> OK, I checked with INFRA on some details and will finish the
> migration
> >> >> tomorrow.
> >> >>
> >> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad 
> wrote:
> >> >>
> >> >>> Awesome, thanks Michael.
> >> >>>
> >> >>> We need to do a little bit of additional configuration to have it
> >> switch
> >> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
> >> the
> >> >>> servers how the site should be published.  I can take care of it
> >> >>> tomorrow.
> >> >>>
> >> >>> Reference:
> >> >>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
> >> >>>
> >> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
> >> mich...@pbandjelly.org>
> >> >>> wrote:
> >> >>>
> >>  committed! :)
> >> 
> >>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
> >> 
> >>  Michael
> >> 
> >>  On 10/3/19 12:22 PM, Jon Haddad wrote:
> >> > I think we can safely ignore them.  Thanks for figuring this out.
> >> >
> >> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
> >> mich...@pbandjelly.org
> >> >
> >> > wrote:
> >> >
> >> >> I'm making progress through many periodic timeouts to svn.a.o and
> >> >> restarts, but it appears that svn2git is smart enough to pick up
> >> where
> >> >> it left off. The first commit captured at the svn path I'm
> >> specifying
> >>  is
> >> >> when Cassandra was moved to a top level project at r922689
> >>  (2010-03-13).
> >> >> I don't know the old incubator path, and it's probably OK to
> ignore
> >>  the
> >> >> few older incubator commits? I imagine it would mean starting
> over
> >> the
> >> >> entire import to pull in those older incubator svn commits, then
> >> >> changing the url and somehow importing the newer path on top?
> >> >>
> >> >> I tried using a local path as the source to try to speed things
> up,
> >> >> after I got my first few timeouts, but that fails.
> >> >>
> >> >> Curious if anyone really cares if we lose a few early commits -
> if
> >>  so, I
> >> >> can try to figure out the old path and start again.
> >> >>
> >> >> Michael
> >> >>
> >> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
> >> >>> Thanks for taking a look, Michael.  Hopefully you have better
> luck
> >>

Re: moving the site from SVN to git

2019-10-30 Thread Jon Haddad

I figured out what was wrong with the site generation, I've pushed up a fix.

I regenerated the site and noticed the blog post for streaming was marked
as deleted, which was odd.  I dug back through the history and found it an
HTML file committed at
http://svn.apache.org/viewvc?view=revision=1857225, but I'm not
sure where the original content is.  (My SVN foo is terrible now)

Looking at the Git history I see this:

commit f00523b1eefc90b5e4515db0d8c3ab207656684b
Author: zznate 
Date:   Wed Apr 10 01:16:07 2019 +

CASSANDRA-14765 - Streaming performance post by Sumanth Pasupuleti

git-svn-id: http://svn.apache.org/repos/asf/cassandra/site@1857225
13f79535-47bb-0310-9956-ffa450edef68

Was this just published directly as HTML?

Nate, do you remember how this was handled?  Am I missing something obvious?

Jon

On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad  wrote:

> I'll take a look at the website generation.  Thanks for fixing manually
> for now.
>
> On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler 
> wrote:
>
>> I have updated the new releases in:
>>src/_data/releases.yaml
>>
>> I ran through the docker build/run, yet the main index and download
>> pages of the site were not modified with the new release versions and
>> dates. I'm going to reset --hard and hand edit those pages. #justFYI
>>
>> Michael
>>
>> On 10/17/19 9:07 AM, Jon Haddad wrote:
>> > The migration is finished.
>> >
>> > I had to fix a few things along the way.  The docker containers didn't
>> > build correctly (based on debian:latest rather than a fixed tag), and
>> the
>> > site had to be served out of the content directory rather than the
>> publish
>> > one we were using.
>> >
>> > I'm going to address a couple things as follow ups.  We still point
>> people
>> > to IRC, I'll update that to slack.  Longer term I'll migrate it to Hugo,
>> > which will make the entire process a lot easier.
>> >
>> > Jon
>> >
>> >
>> >
>> > On Wed, Oct 9, 2019 at 10:26 PM Jon Haddad  wrote:
>> >
>> >> OK, I checked with INFRA on some details and will finish the migration
>> >> tomorrow.
>> >>
>> >> On Thu, Oct 3, 2019 at 11:32 AM Jon Haddad  wrote:
>> >>
>> >>> Awesome, thanks Michael.
>> >>>
>> >>> We need to do a little bit of additional configuration to have it
>> switch
>> >>> over.  Specifically, we need to set up the .asf.yaml config to tell
>> the
>> >>> servers how the site should be published.  I can take care of it
>> >>> tomorrow.
>> >>>
>> >>> Reference:
>> >>>
>> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
>> >>>
>> >>> On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler <
>> mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  committed! :)
>> 
>>  https://gitbox.apache.org/repos/asf?p=cassandra-website.git
>> 
>>  Michael
>> 
>>  On 10/3/19 12:22 PM, Jon Haddad wrote:
>> > I think we can safely ignore them.  Thanks for figuring this out.
>> >
>> > On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler <
>> mich...@pbandjelly.org
>> >
>> > wrote:
>> >
>> >> I'm making progress through many periodic timeouts to svn.a.o and
>> >> restarts, but it appears that svn2git is smart enough to pick up
>> where
>> >> it left off. The first commit captured at the svn path I'm
>> specifying
>>  is
>> >> when Cassandra was moved to a top level project at r922689
>>  (2010-03-13).
>> >> I don't know the old incubator path, and it's probably OK to ignore
>>  the
>> >> few older incubator commits? I imagine it would mean starting over
>> the
>> >> entire import to pull in those older incubator svn commits, then
>> >> changing the url and somehow importing the newer path on top?
>> >>
>> >> I tried using a local path as the source to try to speed things up,
>> >> after I got my first few timeouts, but that fails.
>> >>
>> >> Curious if anyone really cares if we lose a few early commits - if
>>  so, I
>> >> can try to figure out the old path and start again.
>> >>
>> >> Michael
>> >>
>> >> On 10/3/19 11:14 AM, Jon Haddad wrote:
>> >>> Thanks for taking a look, Michael.  Hopefully you have better luck
>>  than
>> >> me
>> >>> :)
>> >>>
>> >>> On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler <
>>  mich...@pbandjelly.org>
>> >>> wrote:
>> >>>
>>  I cloned the empty cassandra-website git repo, and I'm running:
>> 
>>  svn2git http://svn.apache.org/repos/asf/cassandra/site
>>  --rootistrunk
>>  --no-minimize-url
>> 
>>  ..to see what I get. An svn checkout of the above url says it's
>> only
>>  69M, so I suppose it's pulling all history of all time for all
>>  projects?
>> 
>>  I'll let this roll for a while I run an errand and report back!
>> 
>>  Michael
>> 
>>  On

Re: moving the site from SVN to git

Re: moving the site from SVN to git

Re: moving the site from SVN to git

Re: moving the site from SVN to git

Re: moving the site from SVN to git

5 matches

Site Navigation

Mail list logo

Footer information