[chirp_devel] help contributing...
Hi All, Here is a dumb question, but Jens and I have been working back and forth on the TYT TH9800. He is on vacation for a few weeks and I would like to start the new year with an initial cut at the TH9800. I do have mercurial on my Mac where I have been developing and have been doing local commits along the way along with pulls and update from the repository.
In other HG environments I have used I would just do a “push” to send my changes, but I think you are doing something different. So after I do a bit more testing how do I deliver a rather significant change to the th9800.py file?
thanks.
James N1DDK.
On Wed, Dec 31, 2014 at 9:52 AM, jml jml@jmlzone.com wrote:
In other HG environments I have used I would just do a “push” to send my changes, but I think you are doing something different. So after I do a bit more testing how do I deliver a rather significant change to the th9800.py file?
http://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess
After setting up PatchBomb, you can send your latest Mercurial patch with hg email tip
Or for a set of patches, hg email -r nnnn:nnnn
Tom KD7LXL
On Wed, Dec 31, 2014 at 12:52 PM, jml jml@jmlzone.com wrote:
Hi All, Here is a dumb question, but Jens and I have been working back and forth on the TYT TH9800. He is on vacation for a few weeks and I would like to start the new year with an initial cut at the TH9800. I do have mercurial on my Mac where I have been developing and have been doing local commits along the way along with pulls and update from the repository.
In other HG environments I have used I would just do a “push” to send my changes, but I think you are doing something different. So after I do a bit more testing how do I deliver a rather significant change to the th9800.py file?
thanks.
James N1DDK.
Hi James,
The two ways that I know how to do it in my Windows 7 environment are...
HG EXPORT TIP > {SomeFileName}.patch
Then just attach the {SomeFileName}.patch to an email to the "chirp-devel" mailing list.
and the other is (which is the one I use)...
HG EMAIL TIP
Thanks Jim and Tom I will give it a try a bit later in the day :)
On Dec 31, 2014, at 1:02 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Wed, Dec 31, 2014 at 12:52 PM, jml jml@jmlzone.com wrote:
Hi All, Here is a dumb question, but Jens and I have been working back and forth on the TYT TH9800. He is on vacation for a few weeks and I would like to start the new year with an initial cut at the TH9800. I do have mercurial on my Mac where I have been developing and have been doing local commits along the way along with pulls and update from the repository.
In other HG environments I have used I would just do a “push” to send my changes, but I think you are doing something different. So after I do a bit more testing how do I deliver a rather significant change to the th9800.py file?
thanks.
James N1DDK.
Hi James,
The two ways that I know how to do it in my Windows 7 environment are...
HG EXPORT TIP > {SomeFileName}.patch
Then just attach the {SomeFileName}.patch to an email to the "chirp-devel" mailing list.
and the other is (which is the one I use)...
HG EMAIL TIP _______________________________________________ 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
Ok I may have HG screwed myself.
In the past I would hg pull and hg merge before I pushed, So I hg pulled and hg merged and got several changes I did not have before. I have tested my changes and they seem to work.
I tried hg export tip > add_comment.patch and I see everyones changes but mine.
if I hg diff -r2310 -r2311 | more then I see my changes.
when I used hg in the past there was a hg expert in the next cube who could sort out its idiosynchrocies.
Ugh! Sorry.
Suggestions please!
On Dec 31, 2014, at 1:02 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Wed, Dec 31, 2014 at 12:52 PM, jml jml@jmlzone.com wrote:
Hi All, Here is a dumb question, but Jens and I have been working back and forth on the TYT TH9800. He is on vacation for a few weeks and I would like to start the new year with an initial cut at the TH9800. I do have mercurial on my Mac where I have been developing and have been doing local commits along the way along with pulls and update from the repository.
In other HG environments I have used I would just do a “push” to send my changes, but I think you are doing something different. So after I do a bit more testing how do I deliver a rather significant change to the th9800.py file?
thanks.
James N1DDK.
Hi James,
The two ways that I know how to do it in my Windows 7 environment are...
HG EXPORT TIP > {SomeFileName}.patch
Then just attach the {SomeFileName}.patch to an email to the "chirp-devel" mailing list.
and the other is (which is the one I use)...
HG EMAIL TIP _______________________________________________ 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
On Wed, Dec 31, 2014 at 10:54 AM, jml jml@jmlzone.com wrote:
Ok I may have HG screwed myself.
In the past I would hg pull and hg merge before I pushed, So I hg pulled and hg merged and got several changes I did not have before. I have tested my changes and they seem to work.
Since you don't control the upstream repo, the easiest way to temporarily add and remove your commits during development is to use Mq. To pull upstream changes, first remove your patches, update, then add your patches back to the local repo: hg qpop --all hg pull -u hg qpush --all
I tried hg export tip > add_comment.patch and I see everyones changes but mine.
if I hg diff -r2310 -r2311 | more then I see my changes.
Then try: hg export -r 2310:2311 > add_comment.patch or hg email -r 2310:2311
Tom KD7LXL
On Wed, Dec 31, 2014 at 2:00 PM, Tom Hayward tom@tomh.us wrote:
On Wed, Dec 31, 2014 at 10:54 AM, jml jml@jmlzone.com wrote:
Ok I may have HG screwed myself.
In the past I would hg pull and hg merge before I pushed, So I hg pulled and hg merged and got several changes I did not have before. I have tested my changes and they seem to work.
Since you don't control the upstream repo, the easiest way to temporarily add and remove your commits during development is to use Mq. To pull upstream changes, first remove your patches, update, then add your patches back to the local repo: hg qpop --all hg pull -u hg qpush --all
Thanks Tom. I'm sure that this will be useful to me as well.
Jim
participants (3)
-
Jim Unroe -
jml -
Tom Hayward