[chirp_devel] TH UV88

[Cyril Velter]

Thanks,

Seems like the trick is to create a new branch for each change.

cyril

Le mer. 7 févr. 2024 à 00:08, Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> a écrit :

> > I'm not not an expert, but this is what I do
> >
> > I checkout a new branch
> >
> > $ git checkout origin -b test-some-more-drivers
> >
> > Soon after I make the first changes, I commit them
> >
> > $ git commit -a
> >
> > Then as I continue my work, I continue to amend my commit
> >
> > $ git commit -a --amend
>
> Yep, this, but be sure to:
>
> $ git fetch origin
>
> (assuming origin is my repo) as a first step every time, as that's what
> updates your tree from mine. Since the problem is your tree/branch is
> behind, this is important obviously, as git doesn't know and that's why
> it's submitting lots of stuff again.
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20240207/0d77c958/attachment-0001.html