Menu
▾
▴
Re: [Bochs-developers] Before declaring Bochs is dead ...
|
From: <stl...@gm...> - 2022-07-11 11:12:05
|
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
|
