bochs-developers — Bochs Developers Mailing List

Re: [Bochs-developers] Running and building one of the releases

[Gregg L. <gre...@gm...>]

Hello!
Okay folks, it's safe to ignore this one. The source code was
buildable, from source not from a SRC RPM from the regular tar.gz
file.
-----
Gregg C Levine gre...@gm...
"This signature was still fighting the timewars, Time and again."

On Tue, Apr 22, 2025 at 7:49 PM Gregg Levine <gre...@gm...> wrote:
>
> Hello!
> I've gotten one of the releases of Bochs from the site, which is 2.8.1
> in fact.  Now I can run it okay. I've even got DLX to boot, both
> native, and using the GRUB boot loader.. However this is where it got
> strange. I've always been able to build the release to provide some
> understanding of how the whole thing works. This one won't build.
>
> I get a strange error message from the process. Now I'll try again
> trying different later releases, to the most recent, and if need be
> I'll make available those messages.
> -----
> Gregg C Levine gre...@gm...
> "This signature was still fighting the timewars, Time and again."

[Bochs-developers] Running and building one of the releases

[Gregg L. <gre...@gm...>]

Hello!
I've gotten one of the releases of Bochs from the site, which is 2.8.1
in fact.  Now I can run it okay. I've even got DLX to boot, both
native, and using the GRUB boot loader.. However this is where it got
strange. I've always been able to build the release to provide some
understanding of how the whole thing works. This one won't build.

I get a strange error message from the process. Now I'll try again
trying different later releases, to the most recent, and if need be
I'll make available those messages.
-----
Gregg C Levine gre...@gm...
"This signature was still fighting the timewars, Time and again."

[Bochs-developers] Please help me understand STOP_TRACE bit usage in function cpu_loop_debugger

[laurent c. <mar...@gm...>]

Hello,

I'm a UEFI firmware engineer. We sometimes have to do changes very early in
the BIOS flow after cold reset (the few thousands of instructions after the
reset vector) and Bochs and its built-in debugger has been very useful to
test these changes for some years now.

I have upgraded my custom simulator recently to use Bochs 3.0 and I have
run into an issue where the x86 instruction execution loop in function
*cpu_loop_debugger* seems to ignore the STOP_TRACE bit and fetch invalid
instructions beyond taken branches.

More specifically, I'm concerned by this test at line 117 in cpu.cc

      if (BX_CPU_THIS_PTR async_event & ~BX_ASYNC_EVENT_STOP_TRACE) break;

This test breaks the execution loop on all "async events" except STOP_TRACE
so wouldn't it ignore STOP_TRACE bit set by branch instructions?

Moreover this test seems to contradict the purpose of line 93

    // stop tracing after every instruction to handle in internal debugger
    BX_CPU_THIS_PTR async_event |= BX_ASYNC_EVENT_STOP_TRACE;

How can it "stop tracing after every instruction" if the STOP_TRACE bit
isn't tested after executing an instruction?

Hope my question makes sense. Thanks for this very helpful open-source x86
emulator!

[Bochs-developers] testing bochs

[folkert <fo...@va...>]

Hi,

I'm working on an 8088 emulator test set.
The idea is to create a set of tests to validate a new 8088 emulator.
Altough not complete, it tests quite a bit of the instruction-set of
that processor.

I always also verify the test set against a real processor (via a
PI86) so the test should be fine. But I (still) would like to run it
against other emulators, to see if I missed anything or so.
So indeed, I would like to run it against Bochs.

The test set consists of about 6500 assembly (generated) files. They
are assembled into a .bin-file that should be loaded at 0000:0000
and then start to run either at 0000:0000 or (preferably) at
0000:0800. When it encounters a problem, it invokes HLT. If all went
well, it sets SI to $a5ee, sends $ff to i/o-port $80 and then
invokes HLT as well.
This page:
https://stackoverflow.com/questions/6142925/how-can-i-use-bochs-to-run-assembly-code
describes how to start a .bin from the command-line, so that hurdle
is taken. Yet one is left: how can I get bochs to:
- terminate when it reaches a HLT instruction
- log something when it either an i/o port is touched or anything
  else I could do from code?

Thanks.


regards

p.s. the test set is at
https://github.com/folkertvanheusden/8086-processor-emulation-validation-testset
and is released in the public domain

[Bochs-developers] interrupt(): gate descriptor is not valid sys seg

[Werner L. <wl...@gn...>]

Running MS-DOS 6.22 within bochs, my `bochsout.txt` file is
continuously flooded with the following four lines:

```
[CPU0  ] interrupt(): gate descriptor is not valid sys seg (vector=0x28)
[CPU0  ] interrupt(): gate descriptor is not valid sys seg (vector=0x16)
[CPU0  ] interrupt(): gate descriptor is not valid sys seg (vector=0x16)
[CPU0  ] interrupt(): gate descriptor is not valid sys seg (vector=0x16)
```

Is this a known problem?  Am I doing something wrong?  A quick search
in the internet didn't reveal anything.  I'm using boch's default
configuration file, with

```
ata0-master: type=disk, mode=flat, path="/home/wl/.bochs/c.msdos.img", cylinders=0
```

as the only change.


    Werner

Re: [Bochs-developers] math_abort: MSDOS compatibility FPU exception

[Werner L. <wl...@gn...>]

> Around 15 years ago I used bochs to run the MS-DOS programs part of
> 'Score' (a music typesetter from 1994) on my GNU/Linux box – it
> worked then.  Today I retried with bochs version 2.7, and it fails.

Please disregard my e-mail.  I've now tried with original MS-DOS 6.22
instead of FreeBSD, and it works.

Phew :-)


   Werner

[Bochs-developers] math_abort: MSDOS compatibility FPU exception

[Werner L. <wl...@gn...>]

Around 15 years ago I used bochs to run the MS-DOS programs part of
'Score' (a music typesetter from 1994) on my GNU/Linux box – it worked
then.  Today I retried with bochs version 2.7, and it fails.

Unfortunately, I no longer have my old bochs configuration file.  My
data is on a 100MByte disk image containing FreeDOS kernel 1.1.26a
(from April 2002) together with the score binaries (that I no longer
have elsewhere).

All score programs freeze very early after the start.  Looking into
`bochsout.txt` it seems that

```
math_abort: MSDOS compatibility FPU exception
```

is the problem.[*]

What can I do?  Apparently, my bochs resource file is misconfigured...
If necessary, I can provide the disk image privately for testing
purposes; it is only about 5MByte if compressed.


    Werner


[*] I've just compiled bochs 2.3.7 for testing purposes; however, it
    fails the same way.

Re: [Bochs-developers] Timer calculation for hypervisor

[Stanislav S. <stl...@gm...>]

You want to be tickn as big as you can.
But not sure you know how big it can be.
Sometimes when you have no external events expected - you may VMEXIT and
call tickn after 100M instructions.
But sometimes events emerge during the instructions themselves, like store
actually wrote to APIC ICR and caused IPI - you need to be able to handle
it within reasonable time.
If you delay the VMEXIT and tickn you may break your guest. But I cannot
tell what are the conditions for breaking/not breaking the guest ...

Stanislav



On Sun, Jul 17, 2022 at 12:57 PM nick <sti...@gm...> wrote:

> Hi,
>
> Thanks for the reply. My couple of nanoseconds is 0x3000(vmx timer) and
> then i call `bx_pc_system.tickn(0x3000)`. Initially my thought process
> behind this is that the minimum timer(excluding hpet vdev) is around
> 0x3000, so instead doing a vm exit after every instruction and call the
> bochs tickn(), I thought it would be faster to do it for a minimum event
> needed time. I noticed that if I change the vmx timer to `100` and the
> tickn to a big number like `1000000` the execution is way faster. So I
> am trying to figure out what would be the fastest execution. Are you
> suggesting that I should call tick1() after every executed guest
> instruction? I thought that there should be a way based on my host cpu
> to calculate the right timer values.
>
> Thanks,
>
> On 7/17/2022 7:37 AM, stl...@gm... wrote:
> > Couple of nanoseconds might be several execution cycles on your host.
> > Single cache miss with DRAM access is ~10ns.
> > How much is your "couple"?
> >
> > In general Bochs is trying to be as reproducible as possible and
> therefore its time is defined according to x86 instructions execution.
> > 1 tick = 1 instructions.
> > For rep string flows 1 tick = 1 iteration of the repeat.
> > This models machine with exactly 1 IPC
> >
> > -----Original Message-----
> > From: nick <sti...@gm...>
> > Sent: Sunday, 17 July 2022 2:21
> > To: boc...@li...
> > Subject: [Bochs-developers] Timer calculation for hypervisor
> >
> > Greetings,
> >
> > I am doing a fun project, where I am replacing the cpu emulator of bochs
> with a hypervisor(intel vmx).
> >
> > There are virtual devices, like the keyboard controller, that are using
> a timer for certain events.
> >
> > The way I am handling it with the hypervisor is to use a vmx timer
> exit(VMX-preemption timer) every couple nanoseconds and then handle it in
> bochs by calling `bx_pc_system.tickn(timer)`.
> >
> > I noticed that there is a significant execution delay based on the value
> of the timers. I was wondering what is the right way to calculate the timer
> for the fastest execution(both the VMX and the value in bochs).
> >
> > My cpu is `i7-6700K CPU @ 4.00GHz` if that somehow helps with the
> calculation.
> >
> > Thank you,
> >
> >
> >
> >
> >
> > _______________________________________________
> > bochs-developers mailing list
> > boc...@li...
> > https://lists.sourceforge.net/lists/listinfo/bochs-developers
> >
>

Re: [Bochs-developers] Timer calculation for hypervisor

[nick <sti...@gm...>]

Hi,

Thanks for the reply. My couple of nanoseconds is 0x3000(vmx timer) and 
then i call `bx_pc_system.tickn(0x3000)`. Initially my thought process 
behind this is that the minimum timer(excluding hpet vdev) is around 
0x3000, so instead doing a vm exit after every instruction and call the 
bochs tickn(), I thought it would be faster to do it for a minimum event 
needed time. I noticed that if I change the vmx timer to `100` and the 
tickn to a big number like `1000000` the execution is way faster. So I 
am trying to figure out what would be the fastest execution. Are you 
suggesting that I should call tick1() after every executed guest 
instruction? I thought that there should be a way based on my host cpu 
to calculate the right timer values.

Thanks,

On 7/17/2022 7:37 AM, stl...@gm... wrote:
> Couple of nanoseconds might be several execution cycles on your host.
> Single cache miss with DRAM access is ~10ns.
> How much is your "couple"?
>
> In general Bochs is trying to be as reproducible as possible and therefore its time is defined according to x86 instructions execution.
> 1 tick = 1 instructions.
> For rep string flows 1 tick = 1 iteration of the repeat.
> This models machine with exactly 1 IPC
>
> -----Original Message-----
> From: nick <sti...@gm...>
> Sent: Sunday, 17 July 2022 2:21
> To: boc...@li...
> Subject: [Bochs-developers] Timer calculation for hypervisor
>
> Greetings,
>
> I am doing a fun project, where I am replacing the cpu emulator of bochs with a hypervisor(intel vmx).
>
> There are virtual devices, like the keyboard controller, that are using a timer for certain events.
>
> The way I am handling it with the hypervisor is to use a vmx timer exit(VMX-preemption timer) every couple nanoseconds and then handle it in bochs by calling `bx_pc_system.tickn(timer)`.
>
> I noticed that there is a significant execution delay based on the value of the timers. I was wondering what is the right way to calculate the timer for the fastest execution(both the VMX and the value in bochs).
>
> My cpu is `i7-6700K CPU @ 4.00GHz` if that somehow helps with the calculation.
>
> Thank you,
>
>
>
>
>
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers
>

Re: [Bochs-developers] Timer calculation for hypervisor

[<stl...@gm...>]

Couple of nanoseconds might be several execution cycles on your host.
Single cache miss with DRAM access is ~10ns.
How much is your "couple"?

In general Bochs is trying to be as reproducible as possible and therefore its time is defined according to x86 instructions execution.
1 tick = 1 instructions.
For rep string flows 1 tick = 1 iteration of the repeat.
This models machine with exactly 1 IPC

-----Original Message-----
From: nick <sti...@gm...> 
Sent: Sunday, 17 July 2022 2:21
To: boc...@li...
Subject: [Bochs-developers] Timer calculation for hypervisor

Greetings,

I am doing a fun project, where I am replacing the cpu emulator of bochs with a hypervisor(intel vmx).

There are virtual devices, like the keyboard controller, that are using a timer for certain events.

The way I am handling it with the hypervisor is to use a vmx timer exit(VMX-preemption timer) every couple nanoseconds and then handle it in bochs by calling `bx_pc_system.tickn(timer)`.

I noticed that there is a significant execution delay based on the value of the timers. I was wondering what is the right way to calculate the timer for the fastest execution(both the VMX and the value in bochs).

My cpu is `i7-6700K CPU @ 4.00GHz` if that somehow helps with the calculation.

Thank you,





_______________________________________________
bochs-developers mailing list
boc...@li...
https://lists.sourceforge.net/lists/listinfo/bochs-developers

[Bochs-developers] Timer calculation for hypervisor

[nick <sti...@gm...>]

Greetings,

I am doing a fun project, where I am replacing the cpu emulator of bochs 
with a hypervisor(intel vmx).

There are virtual devices, like the keyboard controller, that are using 
a timer for certain events.

The way I am handling it with the hypervisor is to use a vmx timer 
exit(VMX-preemption timer) every couple nanoseconds and then handle it 
in bochs by calling `bx_pc_system.tickn(timer)`.

I noticed that there is a significant execution delay based on the value 
of the timers. I was wondering what is the right way to calculate the 
timer for the fastest execution(both the VMX and the value in bochs).

My cpu is `i7-6700K CPU @ 4.00GHz` if that somehow helps with the 
calculation.

Thank you,

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Colin N. <nic...@gm...>]

Done - https://github.com/stlintel/Bochs/pull/1

On Wed, Jul 13, 2022 at 12:41 PM <stl...@gm...> wrote:

> Please submit a pull request. Want to see how it looks like.
>
> Content doesn’t matter – adding README is good.
>
>
>
> *From:* Colin Nichols <nic...@gm...>
> *Sent:* Wednesday, 13 July 2022 15:20
> *To:* Saulius Krasuckas <sau...@ar...>
> *Cc:* Stanislav <stl...@gm...>; bochs-developers <
> boc...@li...>
> *Subject:* Re: [Bochs-developers] Before declaring Bochs is dead ...
>
>
>
> Hello, I'm very excited to see Bochs moving to Github!
>
>
>
> I'd like to add a README.md to make the repo page a bit less bare.  Maybe
> this would be a good first PR to test out the workflow?
>
>
>
> For now, I'll mostly link into SF for e.g. documentation.  For
> bugs/managing development - is the intention to use Github issues going
> forward?  I would be in favor of this (said as someone who has not
> contributed code... yet)
>
>
>
> > Can someone help with setting up mandatory code review for pull
> > requests ?
>
> I can help with this if you'd like
>
>
>
>
>
> Thank you
>
> Colin
>
>
>
>
>
> On Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <sau...@ar...>
> wrote:
>
> On 2022-07-11 09:26, stl...@gm... wrote:
>
> > Please take a look onto github repository:
> > https://github.com/stlintel/Bochs
> > and also SF git repository:
> > https://sourceforge.net/p/bochs/bochs/ci/master/tree/
>
> Thanks!
>
> > I personally prefer github interface.
>
> Me too. I already starred, forked the repo here, and turned on watching
> (following) it.
>
> > Can someone help with setting up mandatory code review for pull
> > requests ?
>
> Not this time.  But maybe this paragraph or even whole article could
> give some insight:
> https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works
>
> S.
>
>
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers
>
>

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

Please submit a pull request. Want to see how it looks like.

Content doesn’t matter – adding README is good.

 

From: Colin Nichols <nic...@gm...> 
Sent: Wednesday, 13 July 2022 15:20
To: Saulius Krasuckas <sau...@ar...>
Cc: Stanislav <stl...@gm...>; bochs-developers <boc...@li...>
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Hello, I'm very excited to see Bochs moving to Github!

 

I'd like to add a README.md to make the repo page a bit less bare.  Maybe this would be a good first PR to test out the workflow?

 

For now, I'll mostly link into SF for e.g. documentation.  For bugs/managing development - is the intention to use Github issues going forward?  I would be in favor of this (said as someone who has not contributed code... yet)

 

> Can someone help with setting up mandatory code review for pull
> requests ?

I can help with this if you'd like

 

 

Thank you

Colin

 

 

On Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <sau...@ar... <mailto:sau...@ar...> > wrote:

On 2022-07-11 09:26, stl...@gm... <mailto:stl...@gm...>  wrote:

> Please take a look onto github repository:
> https://github.com/stlintel/Bochs
> and also SF git repository:
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/

Thanks!

> I personally prefer github interface.

Me too. I already starred, forked the repo here, and turned on watching 
(following) it.

> Can someone help with setting up mandatory code review for pull 
> requests ?

Not this time.  But maybe this paragraph or even whole article could 
give some insight:
https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works

S.


_______________________________________________
bochs-developers mailing list
boc...@li... <mailto:boc...@li...> 
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Colin N. <nic...@gm...>]

Hello, I'm very excited to see Bochs moving to Github!

I'd like to add a README.md to make the repo page a bit less bare.  Maybe
this would be a good first PR to test out the workflow?

For now, I'll mostly link into SF for e.g. documentation.  For
bugs/managing development - is the intention to use Github issues going
forward?  I would be in favor of this (said as someone who has not
contributed code... yet)

> Can someone help with setting up mandatory code review for pull
> requests ?
I can help with this if you'd like


Thank you
Colin


On Mon, Jul 11, 2022 at 1:57 PM Saulius Krasuckas <sau...@ar...> wrote:

> On 2022-07-11 09:26, stl...@gm... wrote:
>
> > Please take a look onto github repository:
> > https://github.com/stlintel/Bochs
> > and also SF git repository:
> > https://sourceforge.net/p/bochs/bochs/ci/master/tree/
>
> Thanks!
>
> > I personally prefer github interface.
>
> Me too. I already starred, forked the repo here, and turned on watching
> (following) it.
>
> > Can someone help with setting up mandatory code review for pull
> > requests ?
>
> Not this time.  But maybe this paragraph or even whole article could
> give some insight:
> https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works
>
> S.
>
>
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers
>

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Saulius K. <sau...@ar...>]

On 2022-07-11 09:26, stl...@gm... wrote:

> Please take a look onto github repository:
> https://github.com/stlintel/Bochs
> and also SF git repository:
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/

Thanks!

> I personally prefer github interface.

Me too. I already starred, forked the repo here, and turned on watching 
(following) it.

> Can someone help with setting up mandatory code review for pull 
> requests ?

Not this time.  But maybe this paragraph or even whole article could 
give some insight:
https://github.blog/2018-03-23-require-multiple-reviewers/#how-it-works

S.

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Saulius K. <sau...@ar...>]

* On 2022-07-11 14:28, stl...@gm... wrote:
> I also though it could be better to have different layout and avoid
> closing sfsite when you need only Bochs.
> 
> Is it possible to change layout by manipulating current git repo we 
> have got ?

I'm not experienced in this area too.  But... found `git filter-repo` in 
the docs, step 5:
https://docs.github.com/en/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository

And then essential steps 9 and 11, of course.


S.

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Stephen K. <st...@sk...>]

You need to push git tags explicitly:

     git push --tags

Regards,

Stephen


Le 11/07/2022 13:02, stl...@gm... a écrit :

> It is good question why I don't see them there in git tag.
> 
> Seems like they were not uploaded to github for some reason.
> 
> On bare repo that I pushed to guthub I see them all.
> 
> Do you have any idea what I should do to push it with tags ?
> 
> From: Thomas Hemmer <tho...@gm...>
> Sent: Monday, 11 July 2022 11:31
> To: boc...@li...
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Hi folks,
> 
> thanks a lot for your efforts in order to keep bochs alive.
> 
> While taking a look into Stanislav's git repository I missed the 
> release tags there.
> Did you leave them out intentionally?
> 
> Best regards,
> 
> Thomas
> 
> Am 11.07.2022 um 08:26 schrieb stl...@gm...:
> 
> Okay, guys !
> 
> Please take a look onto github repository:
> 
> https://github.com/stlintel/Bochs
> 
> and also SF git repository:
> 
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
> 
> They are identical.
> 
> Could be both cloned and browsed.
> 
> Verify everything you know - this is first time I create new git 
> repositories, not telling about converting from SVN.
> 
> I personally prefer github interface.
> 
> Can someone help with setting up mandatory code review for pull 
> requests ?
> 
> Thanks
> 
> Stansilav
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Monday, 11 July 2022 8:45
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Github suggests next step to do:
> 
> Existing repository using Git
> 
> cd myproject
> 
> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
> 
> git push -u origin master
> 
> Should I ?
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Sunday, 10 July 2022 19:48
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Actually I got some help from folks at work and the conversion is in 
> progress right now.
> 
> It is running from the morning and about 60% done.
> 
> Let's see what is going to be result.
> 
> Thanks,
> 
> Stanislav
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Sunday, 10 July 2022 19:21
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> So you have two suggestions here: (1) have the full name for the author 
> info, and (2) remove the backward pointer to the SVN repo.
> 
> For (1), it looks like the SVN commit history doesn't contain the full 
> name either: Bochs x86 PC emulator / Code / Commit [r14349] 
> (sourceforge.net).  To be consistent, shall we just reuse whatever is 
> in SVN history for the new git repo?
> 
> For (2), I can take a look and see if we can remove the backward 
> pointer.
> 
> Anything else I missed?
> 
> Xinyang
> 
> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
> 
> This is exactly not good one ...
> 
> This is how it supposed to look like:
> 
> == Cut Here ==
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: Volker Ruppert
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> == Cut Here ==
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Saturday, 9 July 2022 18:42
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Did you check https://github.com/countingpine/bochs-svn?  The latest 
> git commit (shown below) matches what I saw from the SVN repo.  They 
> also seem to get the author info and commit message correct (with an 
> additional pointer to the SVN commit).  Is there any issue you saw from 
> the repo?  If not, we can just clone and re-upload the repo to a more 
> official account of Bochs on Github.
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349 
> 6c8e4198-a580-4521-a02f-c9ae86df1db9
> 
> On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
> 
> I see dozens of Bochs forks to git in the net. Most of them outdate and 
> dead.
> 
> Unfortunately not even single one of them is forked properly, with 
> converting authors and cleaning up stuff afterwards.
> 
> Doing simple 'git log' on bochs folder reveals a lot of garbage that 
> should not be there.
> 
> I tried to go through the process of migration from scratch but seems 
> like smth is going wrong for me.
> 
> It prints :
> 
> Initialized empty Git repository in 
> /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
> 
> Using higher level of URL: 
> https://svn.code.sf.net/p/bochs/code/trunk/bochs => 
> https://svn.code.sf.net/p/bochs/code
> 
> And just stuck for very long time. At the end I see .git folder which 
> is empty repo (nothing from SVN was imported).
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Friday, 8 July 2022 22:18
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Totally.  Any open-source project would require the whole community 
> effort to make it live long and prosper, and I think moving Bochs to 
> git/github would encourage more people to contribute (especially 
> nowadays).  Let me know how I can help with the efforts.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Hi,
> 
>> Bochs is one of the highest-fidelity PC emulators and is widely used 
>> in both academia and industry.  If there's a way we can keep it going, 
>> please don't let it die.
> 
> You are the ones who could keep it from doing.
> 
> Bochs can't survive on just 2 contributors which also have families, 
> work and other projects to care.
> 
> We would try to do our best but it can't continue alone.
> 
> On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm...> wrote:
> 
> Hi Stanislav,
> 
> There is a github repo which has its commit history in sync with the 
> SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as 
> a starting point for svn>>git transition or maybe even contact the 
> owner of that github repo for help?
> 
> Bochs is one of the highest-fidelity PC emulators and is widely used in 
> both academia and industry.  If there's a way we can keep it going, 
> please don't let it die.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Ho Folks.
> 
> Seems like I left alone. Tried to write Volker and he didn't respond 
> for 10 days :(
> 
> Before declaring Bochs officially dead I would like to modernize it a 
> bit by moving to newer tools and trying to invite new contributors. I 
> personally like git as new Bochs version control system and especially 
> like github and its code review interface.
> 
> But I am not a master in doing svn>>git transitions.
> 
> In the other side I saw some of you already did it before and have 
> necessary experience.
> 
> Can someone volunteer to have a Zoom/Teams session for the svn>>git 
> transition?
> I hope it won't take forever and as result we should get git repository 
> for Bochs on Sourceforge (seems like they have it) or may be 
> preferable, already in github.
> 
> Anyone ?
> 
> Thanks,
> Stanislav
> 
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________

bochs-developers mailing list

boc...@li...

https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________
bochs-developers mailing list
boc...@li...
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Stephen K. <st...@sk...>]

As long as the repository is public, any user can fork it and make 
changes on their fork, and as long as PRs are enabled (which is the 
default), they can submit PRs.

By default only admins can merge PRs; you can configure additional 
requirements using branch protections in the GH settings. The list of 
contributors is updated as new users add PRs, but it doesn’t confer any 
permissions as such.

I’m wondering about the current layout however; instead of having a 
single Bochs repository with the four sections from SF (bochs, 
bochs-performance, bochs-testing, and sfsite), usual GH practice would 
be to have a Bochs organisation, with four repositories inside that. See 
for example https://github.com/submariner-io/ (which I work on).

Regards,

Stephen


Le 11/07/2022 13:11, stl...@gm... a écrit :
> Now the next question is github management.
> 
> I wish to allow every github user to be able to clone repo or submit
> pull request.
> But only project admins (currently me and Volker) would be able to
> review the pull requests and promote them.
> Currently github says list of contributors is empty meaning I am
> probably the only possible contributor.
> How would it work ?
> Anybody else is allowed to create PR for Bochs ?
> 
> -----Original Message-----
> From: Stephen Kitt <st...@sk...>
> Sent: Monday, 11 July 2022 14:04
> To: stl...@gm...
> Cc: 'Thomas Hemmer' <tho...@gm...>;
> boc...@li...
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> You need to push git tags explicitly:
> 
>      git push --tags
> 
> Regards,
> 
> Stephen
> 
> 
> Le 11/07/2022 13:02, stl...@gm... a écrit :
> 
>> It is good question why I don't see them there in git tag.
>> 
>> Seems like they were not uploaded to github for some reason.
>> 
>> On bare repo that I pushed to guthub I see them all.
>> 
>> Do you have any idea what I should do to push it with tags ?
>> 
>> From: Thomas Hemmer <tho...@gm...>
>> Sent: Monday, 11 July 2022 11:31
>> To: boc...@li...
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Hi folks,
>> 
>> thanks a lot for your efforts in order to keep bochs alive.
>> 
>> While taking a look into Stanislav's git repository I missed the
>> release tags there.
>> Did you leave them out intentionally?
>> 
>> Best regards,
>> 
>> Thomas
>> 
>> Am 11.07.2022 um 08:26 schrieb stl...@gm...:
>> 
>> Okay, guys !
>> 
>> Please take a look onto github repository:
>> 
>> https://github.com/stlintel/Bochs
>> 
>> and also SF git repository:
>> 
>> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
>> 
>> They are identical.
>> 
>> Could be both cloned and browsed.
>> 
>> Verify everything you know - this is first time I create new git
>> repositories, not telling about converting from SVN.
>> 
>> I personally prefer github interface.
>> 
>> Can someone help with setting up mandatory code review for pull
>> requests ?
>> 
>> Thanks
>> 
>> Stansilav
>> 
>> From: stl...@gm... <stl...@gm...>
>> Sent: Monday, 11 July 2022 8:45
>> To: 'Xinyang Ge' <ae...@gm...>
>> Cc: 'bochs-developers' <boc...@li...>
>> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Github suggests next step to do:
>> 
>> Existing repository using Git
>> 
>> cd myproject
>> 
>> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
>> 
>> git push -u origin master
>> 
>> Should I ?
>> 
>> From: stl...@gm... <stl...@gm...>
>> Sent: Sunday, 10 July 2022 19:48
>> To: 'Xinyang Ge' <ae...@gm...>
>> Cc: 'bochs-developers' <boc...@li...>
>> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Actually I got some help from folks at work and the conversion is in
>> progress right now.
>> 
>> It is running from the morning and about 60% done.
>> 
>> Let's see what is going to be result.
>> 
>> Thanks,
>> 
>> Stanislav
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Sunday, 10 July 2022 19:21
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> So you have two suggestions here: (1) have the full name for the
>> author info, and (2) remove the backward pointer to the SVN repo.
>> 
>> For (1), it looks like the SVN commit history doesn't contain the full
>> name either: Bochs x86 PC emulator / Code / Commit [r14349]
>> (sourceforge.net).  To be consistent, shall we just reuse whatever is
>> in SVN history for the new git repo?
>> 
>> For (2), I can take a look and see if we can remove the backward
>> pointer.
>> 
>> Anything else I missed?
>> 
>> Xinyang
>> 
>> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
>> 
>> This is exactly not good one ...
>> 
>> This is how it supposed to look like:
>> 
>> == Cut Here ==
>> 
>> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master,
>> origin/master, origin/HEAD)
>> 
>> Author: Volker Ruppert
>> 
>> Date:   Thu Nov 4 17:44:57 2021 +0000
>> 
>> Updated / improved information about configure shortcut scripts.
>> 
>> == Cut Here ==
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Saturday, 9 July 2022 18:42
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Did you check https://github.com/countingpine/bochs-svn?  The latest
>> git commit (shown below) matches what I saw from the SVN repo.  They
>> also seem to get the author info and commit message correct (with an
>> additional pointer to the SVN commit).  Is there any issue you saw
>> from the repo?  If not, we can just clone and re-upload the repo to a
>> more official account of Bochs on Github.
>> 
>> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master,
>> origin/master, origin/HEAD)
>> 
>> Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
>> 
>> Date:   Thu Nov 4 17:44:57 2021 +0000
>> 
>> Updated / improved information about configure shortcut scripts.
>> 
>> git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349
>> 6c8e4198-a580-4521-a02f-c9ae86df1db9
>> 
>> On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
>> 
>> I see dozens of Bochs forks to git in the net. Most of them outdate
>> and dead.
>> 
>> Unfortunately not even single one of them is forked properly, with
>> converting authors and cleaning up stuff afterwards.
>> 
>> Doing simple 'git log' on bochs folder reveals a lot of garbage that
>> should not be there.
>> 
>> I tried to go through the process of migration from scratch but seems
>> like smth is going wrong for me.
>> 
>> It prints :
>> 
>> Initialized empty Git repository in
>> /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
>> 
>> Using higher level of URL:
>> https://svn.code.sf.net/p/bochs/code/trunk/bochs =>
>> https://svn.code.sf.net/p/bochs/code
>> 
>> And just stuck for very long time. At the end I see .git folder which
>> is empty repo (nothing from SVN was imported).
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Friday, 8 July 2022 22:18
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Totally.  Any open-source project would require the whole community
>> effort to make it live long and prosper, and I think moving Bochs to
>> git/github would encourage more people to contribute (especially
>> nowadays).  Let me know how I can help with the efforts.
>> 
>> Xinyang
>> 
>> On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman
>> <stl...@gm...> wrote:
>> 
>> Hi,
>> 
>>> Bochs is one of the highest-fidelity PC emulators and is widely used
>>> in both academia and industry.  If there's a way we can keep it
>>> going, please don't let it die.
>> 
>> You are the ones who could keep it from doing.
>> 
>> Bochs can't survive on just 2 contributors which also have families,
>> work and other projects to care.
>> 
>> We would try to do our best but it can't continue alone.
>> 
>> On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm...> wrote:
>> 
>> Hi Stanislav,
>> 
>> There is a github repo which has its commit history in sync with the
>> SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as
>> a starting point for svn>>git transition or maybe even contact the
>> owner of that github repo for help?
>> 
>> Bochs is one of the highest-fidelity PC emulators and is widely used
>> in both academia and industry.  If there's a way we can keep it going,
>> please don't let it die.
>> 
>> Xinyang
>> 
>> On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman
>> <stl...@gm...> wrote:
>> 
>> Ho Folks.
>> 
>> Seems like I left alone. Tried to write Volker and he didn't respond
>> for 10 days :(
>> 
>> Before declaring Bochs officially dead I would like to modernize it a
>> bit by moving to newer tools and trying to invite new contributors. I
>> personally like git as new Bochs version control system and especially
>> like github and its code review interface.
>> 
>> But I am not a master in doing svn>>git transitions.
>> 
>> In the other side I saw some of you already did it before and have
>> necessary experience.
>> 
>> Can someone volunteer to have a Zoom/Teams session for the svn>>git
>> transition?
>> I hope it won't take forever and as result we should get git
>> repository for Bochs on Sourceforge (seems like they have it) or may
>> be preferable, already in github.
>> 
>> Anyone ?
>> 
>> Thanks,
>> Stanislav
>> 
>> _______________________________________________
>> bochs-developers mailing list
>> boc...@li...
>> https://lists.sourceforge.net/lists/listinfo/bochs-developers
> 
> _______________________________________________
> 
> bochs-developers mailing list
> 
> boc...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/bochs-developers
> 
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

The SVN2GIT conversion created current layout because SVN was looking like that.
I also though it could be better to have different layout and avoid closing sfsite when you need only Bochs.

Is it possible to change layout by manipulating current git repo we have got ?

-----Original Message-----
From: Stephen Kitt <st...@sk...> 
Sent: Monday, 11 July 2022 14:26
To: stl...@gm...
Cc: 'Thomas Hemmer' <tho...@gm...>; boc...@li...
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

As long as the repository is public, any user can fork it and make changes on their fork, and as long as PRs are enabled (which is the default), they can submit PRs.

By default only admins can merge PRs; you can configure additional requirements using branch protections in the GH settings. The list of contributors is updated as new users add PRs, but it doesn’t confer any permissions as such.

I’m wondering about the current layout however; instead of having a single Bochs repository with the four sections from SF (bochs, bochs-performance, bochs-testing, and sfsite), usual GH practice would be to have a Bochs organisation, with four repositories inside that. See for example https://github.com/submariner-io/ (which I work on).

Regards,

Stephen


Le 11/07/2022 13:11, stl...@gm... a écrit :
> Now the next question is github management.
> 
> I wish to allow every github user to be able to clone repo or submit 
> pull request.
> But only project admins (currently me and Volker) would be able to 
> review the pull requests and promote them.
> Currently github says list of contributors is empty meaning I am 
> probably the only possible contributor.
> How would it work ?
> Anybody else is allowed to create PR for Bochs ?
> 
> -----Original Message-----
> From: Stephen Kitt <st...@sk...>
> Sent: Monday, 11 July 2022 14:04
> To: stl...@gm...
> Cc: 'Thomas Hemmer' <tho...@gm...>; 
> boc...@li...
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> You need to push git tags explicitly:
> 
>      git push --tags
> 
> Regards,
> 
> Stephen
> 
> 
> Le 11/07/2022 13:02, stl...@gm... a écrit :
> 
>> It is good question why I don't see them there in git tag.
>> 
>> Seems like they were not uploaded to github for some reason.
>> 
>> On bare repo that I pushed to guthub I see them all.
>> 
>> Do you have any idea what I should do to push it with tags ?
>> 
>> From: Thomas Hemmer <tho...@gm...>
>> Sent: Monday, 11 July 2022 11:31
>> To: boc...@li...
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Hi folks,
>> 
>> thanks a lot for your efforts in order to keep bochs alive.
>> 
>> While taking a look into Stanislav's git repository I missed the 
>> release tags there.
>> Did you leave them out intentionally?
>> 
>> Best regards,
>> 
>> Thomas
>> 
>> Am 11.07.2022 um 08:26 schrieb stl...@gm...:
>> 
>> Okay, guys !
>> 
>> Please take a look onto github repository:
>> 
>> https://github.com/stlintel/Bochs
>> 
>> and also SF git repository:
>> 
>> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
>> 
>> They are identical.
>> 
>> Could be both cloned and browsed.
>> 
>> Verify everything you know - this is first time I create new git 
>> repositories, not telling about converting from SVN.
>> 
>> I personally prefer github interface.
>> 
>> Can someone help with setting up mandatory code review for pull 
>> requests ?
>> 
>> Thanks
>> 
>> Stansilav
>> 
>> From: stl...@gm... <stl...@gm...>
>> Sent: Monday, 11 July 2022 8:45
>> To: 'Xinyang Ge' <ae...@gm...>
>> Cc: 'bochs-developers' <boc...@li...>
>> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Github suggests next step to do:
>> 
>> Existing repository using Git
>> 
>> cd myproject
>> 
>> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
>> 
>> git push -u origin master
>> 
>> Should I ?
>> 
>> From: stl...@gm... <stl...@gm...>
>> Sent: Sunday, 10 July 2022 19:48
>> To: 'Xinyang Ge' <ae...@gm...>
>> Cc: 'bochs-developers' <boc...@li...>
>> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Actually I got some help from folks at work and the conversion is in 
>> progress right now.
>> 
>> It is running from the morning and about 60% done.
>> 
>> Let's see what is going to be result.
>> 
>> Thanks,
>> 
>> Stanislav
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Sunday, 10 July 2022 19:21
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> So you have two suggestions here: (1) have the full name for the 
>> author info, and (2) remove the backward pointer to the SVN repo.
>> 
>> For (1), it looks like the SVN commit history doesn't contain the 
>> full name either: Bochs x86 PC emulator / Code / Commit [r14349] 
>> (sourceforge.net).  To be consistent, shall we just reuse whatever is 
>> in SVN history for the new git repo?
>> 
>> For (2), I can take a look and see if we can remove the backward 
>> pointer.
>> 
>> Anything else I missed?
>> 
>> Xinyang
>> 
>> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
>> 
>> This is exactly not good one ...
>> 
>> This is how it supposed to look like:
>> 
>> == Cut Here ==
>> 
>> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
>> origin/master, origin/HEAD)
>> 
>> Author: Volker Ruppert
>> 
>> Date:   Thu Nov 4 17:44:57 2021 +0000
>> 
>> Updated / improved information about configure shortcut scripts.
>> 
>> == Cut Here ==
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Saturday, 9 July 2022 18:42
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Did you check https://github.com/countingpine/bochs-svn?  The latest 
>> git commit (shown below) matches what I saw from the SVN repo.  They 
>> also seem to get the author info and commit message correct (with an 
>> additional pointer to the SVN commit).  Is there any issue you saw 
>> from the repo?  If not, we can just clone and re-upload the repo to a 
>> more official account of Bochs on Github.
>> 
>> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
>> origin/master, origin/HEAD)
>> 
>> Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
>> 
>> Date:   Thu Nov 4 17:44:57 2021 +0000
>> 
>> Updated / improved information about configure shortcut scripts.
>> 
>> git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349
>> 6c8e4198-a580-4521-a02f-c9ae86df1db9
>> 
>> On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
>> 
>> I see dozens of Bochs forks to git in the net. Most of them outdate 
>> and dead.
>> 
>> Unfortunately not even single one of them is forked properly, with 
>> converting authors and cleaning up stuff afterwards.
>> 
>> Doing simple 'git log' on bochs folder reveals a lot of garbage that 
>> should not be there.
>> 
>> I tried to go through the process of migration from scratch but seems 
>> like smth is going wrong for me.
>> 
>> It prints :
>> 
>> Initialized empty Git repository in
>> /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
>> 
>> Using higher level of URL:
>> https://svn.code.sf.net/p/bochs/code/trunk/bochs => 
>> https://svn.code.sf.net/p/bochs/code
>> 
>> And just stuck for very long time. At the end I see .git folder which 
>> is empty repo (nothing from SVN was imported).
>> 
>> From: Xinyang Ge <ae...@gm...>
>> Sent: Friday, 8 July 2022 22:18
>> To: Stanislav Shwartsman <stl...@gm...>
>> Cc: bochs-developers <boc...@li...>
>> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
>> 
>> Totally.  Any open-source project would require the whole community 
>> effort to make it live long and prosper, and I think moving Bochs to 
>> git/github would encourage more people to contribute (especially 
>> nowadays).  Let me know how I can help with the efforts.
>> 
>> Xinyang
>> 
>> On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman 
>> <stl...@gm...> wrote:
>> 
>> Hi,
>> 
>>> Bochs is one of the highest-fidelity PC emulators and is widely used 
>>> in both academia and industry.  If there's a way we can keep it 
>>> going, please don't let it die.
>> 
>> You are the ones who could keep it from doing.
>> 
>> Bochs can't survive on just 2 contributors which also have families, 
>> work and other projects to care.
>> 
>> We would try to do our best but it can't continue alone.
>> 
>> On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm...> wrote:
>> 
>> Hi Stanislav,
>> 
>> There is a github repo which has its commit history in sync with the 
>> SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it 
>> as a starting point for svn>>git transition or maybe even contact the 
>> owner of that github repo for help?
>> 
>> Bochs is one of the highest-fidelity PC emulators and is widely used 
>> in both academia and industry.  If there's a way we can keep it 
>> going, please don't let it die.
>> 
>> Xinyang
>> 
>> On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman 
>> <stl...@gm...> wrote:
>> 
>> Ho Folks.
>> 
>> Seems like I left alone. Tried to write Volker and he didn't respond 
>> for 10 days :(
>> 
>> Before declaring Bochs officially dead I would like to modernize it a 
>> bit by moving to newer tools and trying to invite new contributors. I 
>> personally like git as new Bochs version control system and 
>> especially like github and its code review interface.
>> 
>> But I am not a master in doing svn>>git transitions.
>> 
>> In the other side I saw some of you already did it before and have 
>> necessary experience.
>> 
>> Can someone volunteer to have a Zoom/Teams session for the svn>>git 
>> transition?
>> I hope it won't take forever and as result we should get git 
>> repository for Bochs on Sourceforge (seems like they have it) or may 
>> be preferable, already in github.
>> 
>> Anyone ?
>> 
>> Thanks,
>> Stanislav
>> 
>> _______________________________________________
>> bochs-developers mailing list
>> boc...@li...
>> https://lists.sourceforge.net/lists/listinfo/bochs-developers
> 
> _______________________________________________
> 
> bochs-developers mailing list
> 
> boc...@li...
> 
> https://lists.sourceforge.net/lists/listinfo/bochs-developers
> 
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

Now the next question is github management.

I wish to allow every github user to be able to clone repo or submit pull request.
But only project admins (currently me and Volker) would be able to review the pull requests and promote them.
Currently github says list of contributors is empty meaning I am probably the only possible contributor.
How would it work ?
Anybody else is allowed to create PR for Bochs ?

-----Original Message-----
From: Stephen Kitt <st...@sk...> 
Sent: Monday, 11 July 2022 14:04
To: stl...@gm...
Cc: 'Thomas Hemmer' <tho...@gm...>; boc...@li...
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

You need to push git tags explicitly:

     git push --tags

Regards,

Stephen


Le 11/07/2022 13:02, stl...@gm... a écrit :

> It is good question why I don't see them there in git tag.
> 
> Seems like they were not uploaded to github for some reason.
> 
> On bare repo that I pushed to guthub I see them all.
> 
> Do you have any idea what I should do to push it with tags ?
> 
> From: Thomas Hemmer <tho...@gm...>
> Sent: Monday, 11 July 2022 11:31
> To: boc...@li...
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Hi folks,
> 
> thanks a lot for your efforts in order to keep bochs alive.
> 
> While taking a look into Stanislav's git repository I missed the 
> release tags there.
> Did you leave them out intentionally?
> 
> Best regards,
> 
> Thomas
> 
> Am 11.07.2022 um 08:26 schrieb stl...@gm...:
> 
> Okay, guys !
> 
> Please take a look onto github repository:
> 
> https://github.com/stlintel/Bochs
> 
> and also SF git repository:
> 
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
> 
> They are identical.
> 
> Could be both cloned and browsed.
> 
> Verify everything you know - this is first time I create new git 
> repositories, not telling about converting from SVN.
> 
> I personally prefer github interface.
> 
> Can someone help with setting up mandatory code review for pull 
> requests ?
> 
> Thanks
> 
> Stansilav
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Monday, 11 July 2022 8:45
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Github suggests next step to do:
> 
> Existing repository using Git
> 
> cd myproject
> 
> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
> 
> git push -u origin master
> 
> Should I ?
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Sunday, 10 July 2022 19:48
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Actually I got some help from folks at work and the conversion is in 
> progress right now.
> 
> It is running from the morning and about 60% done.
> 
> Let's see what is going to be result.
> 
> Thanks,
> 
> Stanislav
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Sunday, 10 July 2022 19:21
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> So you have two suggestions here: (1) have the full name for the 
> author info, and (2) remove the backward pointer to the SVN repo.
> 
> For (1), it looks like the SVN commit history doesn't contain the full 
> name either: Bochs x86 PC emulator / Code / Commit [r14349] 
> (sourceforge.net).  To be consistent, shall we just reuse whatever is 
> in SVN history for the new git repo?
> 
> For (2), I can take a look and see if we can remove the backward 
> pointer.
> 
> Anything else I missed?
> 
> Xinyang
> 
> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
> 
> This is exactly not good one ...
> 
> This is how it supposed to look like:
> 
> == Cut Here ==
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: Volker Ruppert
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> == Cut Here ==
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Saturday, 9 July 2022 18:42
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Did you check https://github.com/countingpine/bochs-svn?  The latest 
> git commit (shown below) matches what I saw from the SVN repo.  They 
> also seem to get the author info and commit message correct (with an 
> additional pointer to the SVN commit).  Is there any issue you saw 
> from the repo?  If not, we can just clone and re-upload the repo to a 
> more official account of Bochs on Github.
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349
> 6c8e4198-a580-4521-a02f-c9ae86df1db9
> 
> On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
> 
> I see dozens of Bochs forks to git in the net. Most of them outdate 
> and dead.
> 
> Unfortunately not even single one of them is forked properly, with 
> converting authors and cleaning up stuff afterwards.
> 
> Doing simple 'git log' on bochs folder reveals a lot of garbage that 
> should not be there.
> 
> I tried to go through the process of migration from scratch but seems 
> like smth is going wrong for me.
> 
> It prints :
> 
> Initialized empty Git repository in
> /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
> 
> Using higher level of URL: 
> https://svn.code.sf.net/p/bochs/code/trunk/bochs => 
> https://svn.code.sf.net/p/bochs/code
> 
> And just stuck for very long time. At the end I see .git folder which 
> is empty repo (nothing from SVN was imported).
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Friday, 8 July 2022 22:18
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Totally.  Any open-source project would require the whole community 
> effort to make it live long and prosper, and I think moving Bochs to 
> git/github would encourage more people to contribute (especially 
> nowadays).  Let me know how I can help with the efforts.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Hi,
> 
>> Bochs is one of the highest-fidelity PC emulators and is widely used 
>> in both academia and industry.  If there's a way we can keep it 
>> going, please don't let it die.
> 
> You are the ones who could keep it from doing.
> 
> Bochs can't survive on just 2 contributors which also have families, 
> work and other projects to care.
> 
> We would try to do our best but it can't continue alone.
> 
> On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm...> wrote:
> 
> Hi Stanislav,
> 
> There is a github repo which has its commit history in sync with the 
> SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as 
> a starting point for svn>>git transition or maybe even contact the 
> owner of that github repo for help?
> 
> Bochs is one of the highest-fidelity PC emulators and is widely used 
> in both academia and industry.  If there's a way we can keep it going, 
> please don't let it die.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Ho Folks.
> 
> Seems like I left alone. Tried to write Volker and he didn't respond 
> for 10 days :(
> 
> Before declaring Bochs officially dead I would like to modernize it a 
> bit by moving to newer tools and trying to invite new contributors. I 
> personally like git as new Bochs version control system and especially 
> like github and its code review interface.
> 
> But I am not a master in doing svn>>git transitions.
> 
> In the other side I saw some of you already did it before and have 
> necessary experience.
> 
> Can someone volunteer to have a Zoom/Teams session for the svn>>git 
> transition?
> I hope it won't take forever and as result we should get git 
> repository for Bochs on Sourceforge (seems like they have it) or may 
> be preferable, already in github.
> 
> Anyone ?
> 
> Thanks,
> Stanislav
> 
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________

bochs-developers mailing list

boc...@li...

https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________
bochs-developers mailing list
boc...@li...
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

Done

-----Original Message-----
From: Stephen Kitt <st...@sk...> 
Sent: Monday, 11 July 2022 14:04
To: stl...@gm...
Cc: 'Thomas Hemmer' <tho...@gm...>; boc...@li...
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

You need to push git tags explicitly:

     git push --tags

Regards,

Stephen


Le 11/07/2022 13:02, stl...@gm... a écrit :

> It is good question why I don't see them there in git tag.
> 
> Seems like they were not uploaded to github for some reason.
> 
> On bare repo that I pushed to guthub I see them all.
> 
> Do you have any idea what I should do to push it with tags ?
> 
> From: Thomas Hemmer <tho...@gm...>
> Sent: Monday, 11 July 2022 11:31
> To: boc...@li...
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Hi folks,
> 
> thanks a lot for your efforts in order to keep bochs alive.
> 
> While taking a look into Stanislav's git repository I missed the 
> release tags there.
> Did you leave them out intentionally?
> 
> Best regards,
> 
> Thomas
> 
> Am 11.07.2022 um 08:26 schrieb stl...@gm...:
> 
> Okay, guys !
> 
> Please take a look onto github repository:
> 
> https://github.com/stlintel/Bochs
> 
> and also SF git repository:
> 
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
> 
> They are identical.
> 
> Could be both cloned and browsed.
> 
> Verify everything you know - this is first time I create new git 
> repositories, not telling about converting from SVN.
> 
> I personally prefer github interface.
> 
> Can someone help with setting up mandatory code review for pull 
> requests ?
> 
> Thanks
> 
> Stansilav
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Monday, 11 July 2022 8:45
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Github suggests next step to do:
> 
> Existing repository using Git
> 
> cd myproject
> 
> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
> 
> git push -u origin master
> 
> Should I ?
> 
> From: stl...@gm... <stl...@gm...>
> Sent: Sunday, 10 July 2022 19:48
> To: 'Xinyang Ge' <ae...@gm...>
> Cc: 'bochs-developers' <boc...@li...>
> Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Actually I got some help from folks at work and the conversion is in 
> progress right now.
> 
> It is running from the morning and about 60% done.
> 
> Let's see what is going to be result.
> 
> Thanks,
> 
> Stanislav
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Sunday, 10 July 2022 19:21
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> So you have two suggestions here: (1) have the full name for the 
> author info, and (2) remove the backward pointer to the SVN repo.
> 
> For (1), it looks like the SVN commit history doesn't contain the full 
> name either: Bochs x86 PC emulator / Code / Commit [r14349] 
> (sourceforge.net).  To be consistent, shall we just reuse whatever is 
> in SVN history for the new git repo?
> 
> For (2), I can take a look and see if we can remove the backward 
> pointer.
> 
> Anything else I missed?
> 
> Xinyang
> 
> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
> 
> This is exactly not good one ...
> 
> This is how it supposed to look like:
> 
> == Cut Here ==
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: Volker Ruppert
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> == Cut Here ==
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Saturday, 9 July 2022 18:42
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Did you check https://github.com/countingpine/bochs-svn?  The latest 
> git commit (shown below) matches what I saw from the SVN repo.  They 
> also seem to get the author info and commit message correct (with an 
> additional pointer to the SVN commit).  Is there any issue you saw 
> from the repo?  If not, we can just clone and re-upload the repo to a 
> more official account of Bochs on Github.
> 
> commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, 
> origin/master, origin/HEAD)
> 
> Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
> 
> Date:   Thu Nov 4 17:44:57 2021 +0000
> 
> Updated / improved information about configure shortcut scripts.
> 
> git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349
> 6c8e4198-a580-4521-a02f-c9ae86df1db9
> 
> On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
> 
> I see dozens of Bochs forks to git in the net. Most of them outdate 
> and dead.
> 
> Unfortunately not even single one of them is forked properly, with 
> converting authors and cleaning up stuff afterwards.
> 
> Doing simple 'git log' on bochs folder reveals a lot of garbage that 
> should not be there.
> 
> I tried to go through the process of migration from scratch but seems 
> like smth is going wrong for me.
> 
> It prints :
> 
> Initialized empty Git repository in
> /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
> 
> Using higher level of URL: 
> https://svn.code.sf.net/p/bochs/code/trunk/bochs => 
> https://svn.code.sf.net/p/bochs/code
> 
> And just stuck for very long time. At the end I see .git folder which 
> is empty repo (nothing from SVN was imported).
> 
> From: Xinyang Ge <ae...@gm...>
> Sent: Friday, 8 July 2022 22:18
> To: Stanislav Shwartsman <stl...@gm...>
> Cc: bochs-developers <boc...@li...>
> Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...
> 
> Totally.  Any open-source project would require the whole community 
> effort to make it live long and prosper, and I think moving Bochs to 
> git/github would encourage more people to contribute (especially 
> nowadays).  Let me know how I can help with the efforts.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Hi,
> 
>> Bochs is one of the highest-fidelity PC emulators and is widely used 
>> in both academia and industry.  If there's a way we can keep it 
>> going, please don't let it die.
> 
> You are the ones who could keep it from doing.
> 
> Bochs can't survive on just 2 contributors which also have families, 
> work and other projects to care.
> 
> We would try to do our best but it can't continue alone.
> 
> On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm...> wrote:
> 
> Hi Stanislav,
> 
> There is a github repo which has its commit history in sync with the 
> SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as 
> a starting point for svn>>git transition or maybe even contact the 
> owner of that github repo for help?
> 
> Bochs is one of the highest-fidelity PC emulators and is widely used 
> in both academia and industry.  If there's a way we can keep it going, 
> please don't let it die.
> 
> Xinyang
> 
> On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman 
> <stl...@gm...> wrote:
> 
> Ho Folks.
> 
> Seems like I left alone. Tried to write Volker and he didn't respond 
> for 10 days :(
> 
> Before declaring Bochs officially dead I would like to modernize it a 
> bit by moving to newer tools and trying to invite new contributors. I 
> personally like git as new Bochs version control system and especially 
> like github and its code review interface.
> 
> But I am not a master in doing svn>>git transitions.
> 
> In the other side I saw some of you already did it before and have 
> necessary experience.
> 
> Can someone volunteer to have a Zoom/Teams session for the svn>>git 
> transition?
> I hope it won't take forever and as result we should get git 
> repository for Bochs on Sourceforge (seems like they have it) or may 
> be preferable, already in github.
> 
> Anyone ?
> 
> Thanks,
> Stanislav
> 
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________

bochs-developers mailing list

boc...@li...

https://lists.sourceforge.net/lists/listinfo/bochs-developers

_______________________________________________
bochs-developers mailing list
boc...@li...
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

It is good question why I don’t see them there in git tag.

Seems like they were not uploaded to github for some reason.

On bare repo that I pushed to guthub I see them all.

 

Do you have any idea what I should do to push it with tags ?

 

From: Thomas Hemmer <tho...@gm...> 
Sent: Monday, 11 July 2022 11:31
To: boc...@li...
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Hi folks,

thanks a lot for your efforts in order to keep bochs alive.

While taking a look into Stanislav's git repository I missed the release tags there.
Did you leave them out intentionally?


Best regards,

Thomas

 

Am 11.07.2022 um 08:26 schrieb stl...@gm... <mailto:stl...@gm...> :

Okay, guys !

 

Please take a look onto github repository:

https://github.com/stlintel/Bochs

 

and also SF git repository:

https://sourceforge.net/p/bochs/bochs/ci/master/tree/

 

They are identical. 

Could be both cloned and browsed.

Verify everything you know – this is first time I create new git repositories, not telling about converting from SVN.

 

I personally prefer github interface.

Can someone help with setting up mandatory code review for pull requests ?

 

Thanks

Stansilav

 

From: stl...@gm... <mailto:stl...@gm...>   <mailto:stl...@gm...> <stl...@gm...> 
Sent: Monday, 11 July 2022 8:45
To: 'Xinyang Ge'  <mailto:ae...@gm...> <ae...@gm...>
Cc: 'bochs-developers'  <mailto:boc...@li...> <boc...@li...>
Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...

 

Github suggests next step to do:

 

Existing repository using Git

cd myproject

git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs <mailto:ssh://sshwarts@git.code.sf.net/p/bochs/bochs> 

git push -u origin master

 

Should I ?

 

From: stl...@gm... <mailto:stl...@gm...>  <stl...@gm... <mailto:stl...@gm...> > 
Sent: Sunday, 10 July 2022 19:48
To: 'Xinyang Ge' <ae...@gm... <mailto:ae...@gm...> >
Cc: 'bochs-developers' <boc...@li... <mailto:boc...@li...> >
Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...

 

Actually I got some help from folks at work and the conversion is in progress right now.

It is running from the morning and about 60% done.

Let’s see what is going to be result.

 

Thanks,

Stanislav

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Sunday, 10 July 2022 19:21
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

So you have two suggestions here: (1) have the full name for the author info, and (2) remove the backward pointer to the SVN repo.

 

For (1), it looks like the SVN commit history doesn't contain the full name either: Bochs x86 PC emulator / Code / Commit [r14349] (sourceforge.net) <https://sourceforge.net/p/bochs/code/14349/> .  To be consistent, shall we just reuse whatever is in SVN history for the new git repo?

 

For (2), I can take a look and see if we can remove the backward pointer.

 

Anything else I missed?

 

Xinyang

 

On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

This is exactly not good one …

 

This is how it supposed to look like:

 

== Cut Here ==

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: Volker Ruppert

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

== Cut Here ==

 

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Saturday, 9 July 2022 18:42
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Did you check https://github.com/countingpine/bochs-svn?  The latest git commit <https://github.com/countingpine/bochs-svn/commit/d320dadcc9c40282ad282fa6c64ccbfef048d952>  (shown below) matches what I saw from the SVN repo.  They also seem to get the author info and commit message correct (with an additional pointer to the SVN commit).  Is there any issue you saw from the repo?  If not, we can just clone and re-upload the repo to a more official account of Bochs on Github.

 

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

 

    git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349 6c8e4198-a580-4521-a02f-c9ae86df1db9

 

On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

I see dozens of Bochs forks to git in the net. Most of them outdate and dead. 

Unfortunately not even single one of them is forked properly, with converting authors and cleaning up stuff afterwards.

Doing simple ‘git log’ on bochs folder reveals a lot of garbage that should not be there.

 

I tried to go through the process of migration from scratch but seems like smth is going wrong for me.

 

It prints :

 

Initialized empty Git repository in /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/

Using higher level of URL: https://svn.code.sf.net/p/bochs/code/trunk/bochs => https://svn.code.sf.net/p/bochs/code

 

And just stuck for very long time. At the end I see .git folder which is empty repo (nothing from SVN was imported).

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Friday, 8 July 2022 22:18
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Totally.  Any open-source project would require the whole community effort to make it live long and prosper, and I think moving Bochs to git/github would encourage more people to contribute (especially nowadays).  Let me know how I can help with the efforts.

 

Xinyang

 

On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Hi,

 

>Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

You are the ones who could keep it from doing.

Bochs can't survive on just 2 contributors which also have families, work and other projects to care.

We would try to do our best but it can't continue alone.

 

 

On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > wrote:

Hi Stanislav,

 

There is a github repo which has its commit history in sync with the SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as a starting point for svn>>git transition or maybe even contact the owner of that github repo for help?

 

Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

Xinyang

 

 

 

On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Ho Folks.

Seems like I left alone. Tried to write Volker and he didn't respond for 10 days :(

Before declaring Bochs officially dead I would like to modernize it a bit by moving to newer tools and trying to invite new contributors. I personally like git as new Bochs version control system and especially like github and its code review interface.

But I am not a master in doing svn>>git transitions. 

In the other side I saw some of you already did it before and have necessary experience.

Can someone volunteer to have a Zoom/Teams session for the svn>>git transition?
I hope it won't take forever and as result we should get git repository for Bochs on Sourceforge (seems like they have it) or may be preferable, already in github.

Anyone ?

Thanks,
Stanislav

_______________________________________________
bochs-developers mailing list
boc...@li... <mailto:boc...@li...> 
https://lists.sourceforge.net/lists/listinfo/bochs-developers






_______________________________________________
bochs-developers mailing list
boc...@li... <mailto:boc...@li...> 
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[Thomas H. <tho...@gm...>]

Hi folks,

thanks a lot for your efforts in order to keep bochs alive.

While taking a look into Stanislav's git repository I missed the release
tags there.
Did you leave them out intentionally?


Best regards,

Thomas


Am 11.07.2022 um 08:26 schrieb stl...@gm...:
>
> Okay, guys !
>
> Please take a look onto github repository:
>
> https://github.com/stlintel/Bochs
>
> and also SF git repository:
>
> https://sourceforge.net/p/bochs/bochs/ci/master/tree/
>
> They are identical.
>
> Could be both cloned and browsed.
>
> Verify everything you know – this is first time I create new git
> repositories, not telling about converting from SVN.
>
> I personally prefer github interface.
>
> Can someone help with setting up mandatory code review for pull requests ?
>
> Thanks
>
> Stansilav
>
> *From:*stl...@gm... <stl...@gm...>
> *Sent:* Monday, 11 July 2022 8:45
> *To:* 'Xinyang Ge' <ae...@gm...>
> *Cc:* 'bochs-developers' <boc...@li...>
> *Subject:* RE: [Bochs-developers] Before declaring Bochs is dead ...
>
> Github suggests next step to do:
>
> **
>
> *Existing repository using Git*
>
> cd myproject
>
> git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs
>
> git push -u origin master
>
> Should I ?
>
> *From:*stl...@gm... <stl...@gm...>
> *Sent:* Sunday, 10 July 2022 19:48
> *To:* 'Xinyang Ge' <ae...@gm...>
> *Cc:* 'bochs-developers' <boc...@li...>
> *Subject:* RE: [Bochs-developers] Before declaring Bochs is dead ...
>
> Actually I got some help from folks at work and the conversion is in
> progress right now.
>
> It is running from the morning and about 60% done.
>
> Let’s see what is going to be result.
>
> Thanks,
>
> Stanislav
>
> *From:*Xinyang Ge <ae...@gm...>
> *Sent:* Sunday, 10 July 2022 19:21
> *To:* Stanislav Shwartsman <stl...@gm...>
> *Cc:* bochs-developers <boc...@li...>
> *Subject:* Re: [Bochs-developers] Before declaring Bochs is dead ...
>
> So you have two suggestions here: (1) have the full name for the
> author info, and (2) remove the backward pointer to the SVN repo.
>
> For (1), it looks like the SVN commit history doesn't contain the full
> name either: Bochs x86 PC emulator / Code / Commit [r14349]
> (sourceforge.net) <https://sourceforge.net/p/bochs/code/14349/>.  To
> be consistent, shall we just reuse whatever is in SVN history for the
> new git repo?
>
> For (2), I can take a look and see if we can remove the backward pointer.
>
> Anything else I missed?
>
> Xinyang
>
> On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm...> wrote:
>
>     This is exactly not good one …
>
>     This is how it supposed to look like:
>
>     == Cut Here ==
>
>     commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master,
>     origin/master, origin/HEAD)
>
>     Author: Volker Ruppert
>
>     Date:   Thu Nov 4 17:44:57 2021 +0000
>
>         Updated / improved information about configure shortcut scripts.
>
>     == Cut Here ==
>
>     *From:*Xinyang Ge <ae...@gm...>
>     *Sent:* Saturday, 9 July 2022 18:42
>     *To:* Stanislav Shwartsman <stl...@gm...>
>     *Cc:* bochs-developers <boc...@li...>
>     *Subject:* Re: [Bochs-developers] Before declaring Bochs is dead ...
>
>     Did you check https://github.com/countingpine/bochs-svn? The
>     latest git commit
>     <https://github.com/countingpine/bochs-svn/commit/d320dadcc9c40282ad282fa6c64ccbfef048d952>
>     (shown below) matches what I saw from the SVN repo.  They also
>     seem to get the author info and commit message correct (with an
>     additional pointer to the SVN commit).  Is there any issue you saw
>     from the repo?  If not, we can just clone and re-upload the repo
>     to a more official account of Bochs on Github.
>
>     commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master,
>     origin/master, origin/HEAD)
>
>     Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>
>
>     Date:   Thu Nov 4 17:44:57 2021 +0000
>
>         Updated / improved information about configure shortcut scripts.
>
>         git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349
>     6c8e4198-a580-4521-a02f-c9ae86df1db9
>
>     On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm...> wrote:
>
>         I see dozens of Bochs forks to git in the net. Most of them
>         outdate and dead.
>
>         Unfortunately not even single one of them is forked properly,
>         with converting authors and cleaning up stuff afterwards.
>
>         Doing simple ‘git log’ on bochs folder reveals a lot of
>         garbage that should not be there.
>
>         I tried to go through the process of migration from scratch
>         but seems like smth is going wrong for me.
>
>         It prints :
>
>         Initialized empty Git repository in
>         /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/
>
>         Using higher level of URL:
>         https://svn.code.sf.net/p/bochs/code/trunk/bochs =>
>         https://svn.code.sf.net/p/bochs/code
>
>         And just stuck for very long time. At the end I see .git
>         folder which is empty repo (nothing from SVN was imported).
>
>         *From:*Xinyang Ge <ae...@gm...>
>         *Sent:* Friday, 8 July 2022 22:18
>         *To:* Stanislav Shwartsman <stl...@gm...>
>         *Cc:* bochs-developers <boc...@li...>
>         *Subject:* Re: [Bochs-developers] Before declaring Bochs is
>         dead ...
>
>         Totally.  Any open-source project would require the whole
>         community effort to make it live long and prosper, and I think
>         moving Bochs to git/github would encourage more people to
>         contribute (especially nowadays).  Let me know how I can help
>         with the efforts.
>
>         Xinyang
>
>         On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman
>         <stl...@gm...> wrote:
>
>             Hi,
>
>             >Bochs is one of the highest-fidelity PC emulators and is widely used in both
>             academia and industry.  If there's a way we can keep it
>             going, please don't let it die.
>
>             You are the ones who could keep it from doing.
>
>             Bochs can't survive on just 2 contributors which also have
>             families, work and other projects to care.
>
>             We would try to do our best but it can't continue alone.
>
>             On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge
>             <ae...@gm...> wrote:
>
>                 Hi Stanislav,
>
>                 There is a github repo which has its commit history in
>                 sync with the SVN repo:
>                 https://github.com/countingpine/bochs-svn. Can we use
>                 it as a starting point for svn>>git transition or
>                 maybe even contact the owner of that github repo for help?
>
>                 Bochs is one of the highest-fidelity PC emulators and
>                 is widely used in both academia and industry.  If
>                 there's a way we can keep it going, please don't let
>                 it die.
>
>                 Xinyang
>
>                 On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman
>                 <stl...@gm...> wrote:
>
>                     Ho Folks.
>
>                     Seems like I left alone. Tried to write Volker and
>                     he didn't respond for 10 days :(
>
>                     Before declaring Bochs officially dead I would
>                     like to modernize it a bit by moving to newer
>                     tools and trying to invite new contributors. I
>                     personally like git as new Bochs version control
>                     system and especially like github and its code
>                     review interface.
>
>                     But I am not a master in doing svn>>git transitions.
>
>                     In the other side I saw some of you already did it
>                     before and have necessary experience.
>
>                     Can someone volunteer to have a Zoom/Teams session
>                     for the svn>>git transition?
>                     I hope it won't take forever and as result we
>                     should get git repository for Bochs on Sourceforge
>                     (seems like they have it) or may be preferable,
>                     already in github.
>
>                     Anyone ?
>
>                     Thanks,
>                     Stanislav
>
>                     _______________________________________________
>                     bochs-developers mailing list
>                     boc...@li...
>                     https://lists.sourceforge.net/lists/listinfo/bochs-developers
>
>
>
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

Okay, guys !

 

Please take a look onto github repository:

https://github.com/stlintel/Bochs

 

and also SF git repository:

https://sourceforge.net/p/bochs/bochs/ci/master/tree/

 

They are identical. 

Could be both cloned and browsed.

Verify everything you know – this is first time I create new git repositories, not telling about converting from SVN.

 

I personally prefer github interface.

Can someone help with setting up mandatory code review for pull requests ?

 

Thanks

Stansilav

 

From: stl...@gm... <stl...@gm...> 
Sent: Monday, 11 July 2022 8:45
To: 'Xinyang Ge' <ae...@gm...>
Cc: 'bochs-developers' <boc...@li...>
Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...

 

Github suggests next step to do:

 

Existing repository using Git

cd myproject

git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs

git push -u origin master

 

Should I ?

 

From: stl...@gm... <mailto:stl...@gm...>  <stl...@gm... <mailto:stl...@gm...> > 
Sent: Sunday, 10 July 2022 19:48
To: 'Xinyang Ge' <ae...@gm... <mailto:ae...@gm...> >
Cc: 'bochs-developers' <boc...@li... <mailto:boc...@li...> >
Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...

 

Actually I got some help from folks at work and the conversion is in progress right now.

It is running from the morning and about 60% done.

Let’s see what is going to be result.

 

Thanks,

Stanislav

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Sunday, 10 July 2022 19:21
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

So you have two suggestions here: (1) have the full name for the author info, and (2) remove the backward pointer to the SVN repo.

 

For (1), it looks like the SVN commit history doesn't contain the full name either: Bochs x86 PC emulator / Code / Commit [r14349] (sourceforge.net) <https://sourceforge.net/p/bochs/code/14349/> .  To be consistent, shall we just reuse whatever is in SVN history for the new git repo?

 

For (2), I can take a look and see if we can remove the backward pointer.

 

Anything else I missed?

 

Xinyang

 

On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

This is exactly not good one …

 

This is how it supposed to look like:

 

== Cut Here ==

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: Volker Ruppert

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

== Cut Here ==

 

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Saturday, 9 July 2022 18:42
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Did you check https://github.com/countingpine/bochs-svn?  The latest git commit <https://github.com/countingpine/bochs-svn/commit/d320dadcc9c40282ad282fa6c64ccbfef048d952>  (shown below) matches what I saw from the SVN repo.  They also seem to get the author info and commit message correct (with an additional pointer to the SVN commit).  Is there any issue you saw from the repo?  If not, we can just clone and re-upload the repo to a more official account of Bochs on Github.

 

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

 

    git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349 6c8e4198-a580-4521-a02f-c9ae86df1db9

 

On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

I see dozens of Bochs forks to git in the net. Most of them outdate and dead. 

Unfortunately not even single one of them is forked properly, with converting authors and cleaning up stuff afterwards.

Doing simple ‘git log’ on bochs folder reveals a lot of garbage that should not be there.

 

I tried to go through the process of migration from scratch but seems like smth is going wrong for me.

 

It prints :

 

Initialized empty Git repository in /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/

Using higher level of URL: https://svn.code.sf.net/p/bochs/code/trunk/bochs => https://svn.code.sf.net/p/bochs/code

 

And just stuck for very long time. At the end I see .git folder which is empty repo (nothing from SVN was imported).

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Friday, 8 July 2022 22:18
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Totally.  Any open-source project would require the whole community effort to make it live long and prosper, and I think moving Bochs to git/github would encourage more people to contribute (especially nowadays).  Let me know how I can help with the efforts.

 

Xinyang

 

On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Hi,

 

>Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

You are the ones who could keep it from doing.

Bochs can't survive on just 2 contributors which also have families, work and other projects to care.

We would try to do our best but it can't continue alone.

 

 

On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > wrote:

Hi Stanislav,

 

There is a github repo which has its commit history in sync with the SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as a starting point for svn>>git transition or maybe even contact the owner of that github repo for help?

 

Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

Xinyang

 

 

 

On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Ho Folks.

Seems like I left alone. Tried to write Volker and he didn't respond for 10 days :(

Before declaring Bochs officially dead I would like to modernize it a bit by moving to newer tools and trying to invite new contributors. I personally like git as new Bochs version control system and especially like github and its code review interface.

But I am not a master in doing svn>>git transitions. 

In the other side I saw some of you already did it before and have necessary experience.

Can someone volunteer to have a Zoom/Teams session for the svn>>git transition?
I hope it won't take forever and as result we should get git repository for Bochs on Sourceforge (seems like they have it) or may be preferable, already in github.

Anyone ?

Thanks,
Stanislav

_______________________________________________
bochs-developers mailing list
boc...@li... <mailto:boc...@li...> 
https://lists.sourceforge.net/lists/listinfo/bochs-developers

Re: [Bochs-developers] Before declaring Bochs is dead ...

[<stl...@gm...>]

Github suggests next step to do:

 

Existing repository using Git

cd myproject

git remote add origin ssh://sshwarts@git.code.sf.net/p/bochs/bochs

git push -u origin master

 

Should I ?

 

From: stl...@gm... <stl...@gm...> 
Sent: Sunday, 10 July 2022 19:48
To: 'Xinyang Ge' <ae...@gm...>
Cc: 'bochs-developers' <boc...@li...>
Subject: RE: [Bochs-developers] Before declaring Bochs is dead ...

 

Actually I got some help from folks at work and the conversion is in progress right now.

It is running from the morning and about 60% done.

Let’s see what is going to be result.

 

Thanks,

Stanislav

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Sunday, 10 July 2022 19:21
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

So you have two suggestions here: (1) have the full name for the author info, and (2) remove the backward pointer to the SVN repo.

 

For (1), it looks like the SVN commit history doesn't contain the full name either: Bochs x86 PC emulator / Code / Commit [r14349] (sourceforge.net) <https://sourceforge.net/p/bochs/code/14349/> .  To be consistent, shall we just reuse whatever is in SVN history for the new git repo?

 

For (2), I can take a look and see if we can remove the backward pointer.

 

Anything else I missed?

 

Xinyang

 

On Sat, Jul 9, 2022 at 10:57 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

This is exactly not good one …

 

This is how it supposed to look like:

 

== Cut Here ==

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: Volker Ruppert

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

== Cut Here ==

 

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Saturday, 9 July 2022 18:42
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li...>
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Did you check https://github.com/countingpine/bochs-svn?  The latest git commit <https://github.com/countingpine/bochs-svn/commit/d320dadcc9c40282ad282fa6c64ccbfef048d952>  (shown below) matches what I saw from the SVN repo.  They also seem to get the author info and commit message correct (with an additional pointer to the SVN commit).  Is there any issue you saw from the repo?  If not, we can just clone and re-upload the repo to a more official account of Bochs on Github.

 

commit d320dadcc9c40282ad282fa6c64ccbfef048d952 (HEAD -> master, origin/master, origin/HEAD)

Author: vruppert <vruppert@6c8e4198-a580-4521-a02f-c9ae86df1db9>

Date:   Thu Nov 4 17:44:57 2021 +0000

 

    Updated / improved information about configure shortcut scripts.

 

    git-svn-id: http://svn.code.sf.net/p/bochs/code/trunk@14349 6c8e4198-a580-4521-a02f-c9ae86df1db9

 

On Sat, Jul 9, 2022 at 7:24 AM <stl...@gm... <mailto:stl...@gm...> > wrote:

I see dozens of Bochs forks to git in the net. Most of them outdate and dead. 

Unfortunately not even single one of them is forked properly, with converting authors and cleaning up stuff afterwards.

Doing simple ‘git log’ on bochs folder reveals a lot of garbage that should not be there.

 

I tried to go through the process of migration from scratch but seems like smth is going wrong for me.

 

It prints :

 

Initialized empty Git repository in /cygdrive/e/BOCHS/BOCHS/SVN/bochs-git-conversion/bochs-git-tmp/.git/

Using higher level of URL: https://svn.code.sf.net/p/bochs/code/trunk/bochs => https://svn.code.sf.net/p/bochs/code

 

And just stuck for very long time. At the end I see .git folder which is empty repo (nothing from SVN was imported).

 

From: Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > 
Sent: Friday, 8 July 2022 22:18
To: Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> >
Cc: bochs-developers <boc...@li... <mailto:boc...@li...> >
Subject: Re: [Bochs-developers] Before declaring Bochs is dead ...

 

Totally.  Any open-source project would require the whole community effort to make it live long and prosper, and I think moving Bochs to git/github would encourage more people to contribute (especially nowadays).  Let me know how I can help with the efforts.

 

Xinyang

 

On Fri, Jul 8, 2022 at 11:03 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Hi,

 

>Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

You are the ones who could keep it from doing.

Bochs can't survive on just 2 contributors which also have families, work and other projects to care.

We would try to do our best but it can't continue alone.

 

 

On Fri, Jul 8, 2022 at 7:05 PM Xinyang Ge <ae...@gm... <mailto:ae...@gm...> > wrote:

Hi Stanislav,

 

There is a github repo which has its commit history in sync with the SVN repo: https://github.com/countingpine/bochs-svn.  Can we use it as a starting point for svn>>git transition or maybe even contact the owner of that github repo for help?

 

Bochs is one of the highest-fidelity PC emulators and is widely used in both academia and industry.  If there's a way we can keep it going, please don't let it die.

 

Xinyang

 

 

 

On Fri, Jul 8, 2022 at 8:48 AM Stanislav Shwartsman <stl...@gm... <mailto:stl...@gm...> > wrote:

Ho Folks.

Seems like I left alone. Tried to write Volker and he didn't respond for 10 days :(

Before declaring Bochs officially dead I would like to modernize it a bit by moving to newer tools and trying to invite new contributors. I personally like git as new Bochs version control system and especially like github and its code review interface.

But I am not a master in doing svn>>git transitions. 

In the other side I saw some of you already did it before and have necessary experience.

Can someone volunteer to have a Zoom/Teams session for the svn>>git transition?
I hope it won't take forever and as result we should get git repository for Bochs on Sourceforge (seems like they have it) or may be preferable, already in github.

Anyone ?

Thanks,
Stanislav

_______________________________________________
bochs-developers mailing list
boc...@li... <mailto:boc...@li...> 
https://lists.sourceforge.net/lists/listinfo/bochs-developers