Hi Stef,
I have also started a short tutorial on setting up Git and GitHub: https://github.com/xymon-monitoring/xymon/pull/13
It was initially written for my own use, as I mainly work with basic Git workflows, and writing it helped me consolidate my understanding.
The content is intentionally concise, practical, and easy to follow. If it can help you or others, that is a plus; in any case, it was already useful for me.
Please note that it may contain some errors...
Bruno
Le 27.01.2026 à 12:03, Stef Coene a écrit :
Hi,
I didn't realised that the sandbox directory was also copied. So no, an other repo is not needed.
And thanks for the chatgpt commands :)
Stef
On 2026-01-27 10:20, Bruno Manzoni via Xymon wrote:
Hi Stef, Seem to me that it is already archive at https://github.com/xymon-monitoring/xymon-svn-mirror/tree/sandbox/ Do you think we need more ?
Below the process to import it (Chatgpt: check!) Let me know if you want me to do it Bruno
Chatgpt: Here is the clean, standard way to do it, without rewriting history.
*Goal*: copy |sandbox/WinPSClient| from |xymon-svn-mirror| into |xymon-client-windows-powershell|.
Steps
1.
Clone the new repo
|git clone https://github.com/xymon-monitoring/xymon-client-windows- powershell cd xymon-client-windows-powershell |
2.
Add the svn mirror as a temporary remote
|git remote add svn-mirror https://github.com/xymon-monitoring/xymon- svn-mirror git fetch svn-mirror |
3.
Extract only the folder you want
|git checkout svn-mirror/master -- sandbox/WinPSClient |
4.
Move contents to repo root (recommended)
|mv sandbox/WinPSClient/* . rm -rf sandbox |
5.
Commit
|git add . git commit -m "Import WinPSClient from xymon svn mirror" |
6.
Push
|git push origin main |
Result
*
Clean new repo
*
Correct history point-in-time
*
No svn noise
*
Easy to evolve independently
This is the right approach for a client split.
Le 27.01.2026 à 09:41, Stef Coene a écrit :
Hi,
I think it's a good idea to keep the sourceforge version data 'as is' for archival purposes. Can you also create a xymon-client-windows-powershell-sourceforge repository? I will upload the sourceforge version and then this repository can be archived.
Stef
On 2026-01-27 07:22, Bruno Manzoni via Xymon wrote:
Hi Nicola, hi Stef,
Following our chat, I created a repo named *xymon-client-windows- powershell*.
Looks OK to me.
Bruno
Le 26.01.2026 à 11:41, Stef Coene a écrit :
Hi,
I don't know how many clients are not natively supported. The Powershell Windows client is one, maybe Mac?
So for this one: xymon-client-windows-powershell
Stef
On 2026-01-26 10:12, Nicola wrote:
I think it's a good idea: should we name it xymon-client-win-ps? The idea is xymon-<type>-<os>-<language> so we can have some uniformity if more come
Nicola
Il giorno 26 gennaio 2026, alle ore 08:39, Stef Coene <xymon@xymon.com <mailto:xymon@xymon.com>> ha scritto:
> Hi, > > I create a private github repository and tried to merge all the > changes I made to the Windows Powershell client. > > But I realised it is better to create a repo in https:// > github.com/ xymon-monitoring/ with v2.42 from https:// > sourceforge.net/p/xymon/ code/HEAD/tree/sandbox/WinPSClient/. > Then I can fork that repo and add my changes. > > > So is it ok if I create a XymonPSClient repository and add > client v2.42 to it? > > > Stef > _______________________________________________ > Xymon mailing list -- xymon@xymon.com > To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com
Xymon mailing list -- xymon@xymon.com To unsubscribe send an email to xymon-leave@xymon.com