[chirp_devel] Old Newbie question
Chirp Development Gurus,
I haven't done any formal software development/maintenance for years (I'm retired), and am only vaguely familiar with git (I can download code with it). Yeah, I'm from the dark ages of RCS, CVS, SVN, etc.
I've got code to add the Retevis RT20 to the existing radtel_rt18.py driver. There's an existing (5 year old) request to add the RT20 in the system (#6067). I added to the existing request to indicate I've got working code, and uploaded a .diff file (yeah, nobody does that any more, but I didn't want the work to get lost...).
Is there a brief tutorial on how to submit a proposed change with git?
(Yeah, when I was working on my RT-21V, I sent the changes to Jim, KC9HI, who was kind/patient enough to add it... but I'd like to move into the 21st century and learn how to do it right.)
73, Paul, K9PS -- Yeah, I'm an old timer. That's not even a vanity call :-)
Hi Paul,
I haven't done any formal software development/maintenance for years (I'm retired), and am only vaguely familiar with git (I can download code with it). Yeah, I'm from the dark ages of RCS, CVS, SVN, etc.
Me too, you're in good company, don't worry :)
I've got code to add the Retevis RT20 to the existing radtel_rt18.py driver. There's an existing (5 year old) request to add the RT20 in the system (#6067). I added to the existing request to indicate I've got working code, and uploaded a .diff file (yeah, nobody does that any more, but I didn't want the work to get lost...).
Is there a brief tutorial on how to submit a proposed change with git?
It's not just git, but github you need to get familiar with. The good news is that there are approximately billions of github tutorials out there. So find one that suits your learning style (text, video, etc) and follow it. It's the same for CHIRP as any other github project.
Roughly it will be:
1. Fork my repo on github. This creates a copy of the repo for yourself. 2. Clone it to your machine with git 3. Create a topic branch from master, make your changes and commit them 4. Push that branch up to your repo 5. Create a pull request from your branch to my repo and wait for me to merge it or complain about something
There's a command-line tool called "gh" which automates a lot of that process for you. Unless you're already used to using git exclusively, I'd spend a few minutes getting that and using it. I think you can probably fork, checkout and submit a PR completely from that tool if you want.
--Dan
Thanks for the reply, Dan,
I also got an email from Jim (KC9HI) with some good notes. Hopefully I'll get the RT20 up there soon.
73, Paul
On Sep 6, 2023, 6:28 PM, at 6:28 PM, Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Hi Paul,
I haven't done any formal software development/maintenance for years (I'm retired), and am only vaguely familiar with git (I can download code with it). Yeah, I'm from the dark ages of RCS, CVS, SVN, etc.
Me too, you're in good company, don't worry :)
I've got code to add the Retevis RT20 to the existing radtel_rt18.py driver. There's an existing (5 year old) request to add the RT20 in the system (#6067). I added to the existing request to indicate I've got working code, and uploaded a .diff file (yeah, nobody does that
any
more, but I didn't want the work to get lost...).
Is there a brief tutorial on how to submit a proposed change with
git?
It's not just git, but github you need to get familiar with. The good news is that there are approximately billions of github tutorials out there. So find one that suits your learning style (text, video, etc) and follow it. It's the same for CHIRP as any other github project.
Roughly it will be:
- Fork my repo on github. This creates a copy of the repo for
yourself. 2. Clone it to your machine with git 3. Create a topic branch from master, make your changes and commit them 4. Push that branch up to your repo 5. Create a pull request from your branch to my repo and wait for me to merge it or complain about something
There's a command-line tool called "gh" which automates a lot of that process for you. Unless you're already used to using git exclusively, I'd spend a few minutes getting that and using it. I think you can probably fork, checkout and submit a PR completely from that tool if you want.
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
With a lot of assistance from KC9HI, I *think* I got everything up into github to get the Retevis RT20 into Chirp. Advise advise if I need to do anything else. Still learning :-)
On Wed, 2023-09-06 at 15:27 -0700, Dan Smith via chirp_devel wrote:
Hi Paul,
I haven't done any formal software development/maintenance for years (I'm retired), and am only vaguely familiar with git (I can download code with it). Yeah, I'm from the dark ages of RCS, CVS, SVN, etc.
Me too, you're in good company, don't worry :)
I've got code to add the Retevis RT20 to the existing radtel_rt18.py driver. There's an existing (5 year old) request to add the RT20 in the system (#6067). I added to the existing request to indicate I've got working code, and uploaded a .diff file (yeah, nobody does that any more, but I didn't want the work to get lost...).
Is there a brief tutorial on how to submit a proposed change with git?
It's not just git, but github you need to get familiar with. The good news is that there are approximately billions of github tutorials out there. So find one that suits your learning style (text, video, etc) and follow it. It's the same for CHIRP as any other github project.
Roughly it will be:
- Fork my repo on github. This creates a copy of the repo for
yourself. 2. Clone it to your machine with git 3. Create a topic branch from master, make your changes and commit them 4. Push that branch up to your repo 5. Create a pull request from your branch to my repo and wait for me to merge it or complain about something
There's a command-line tool called "gh" which automates a lot of that process for you. Unless you're already used to using git exclusively, I'd spend a few minutes getting that and using it. I think you can probably fork, checkout and submit a PR completely from that tool if you want.
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (4)
-
Dan Smith -
Paul L Schmidt -
Paul L. Schmidt
-
Paul Schmidt