<div dir="ltr"><div>Thanks,</div><div><br></div><div>Seems like the trick is to create a new branch for each change.</div><div><br></div><div>cyril<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 7 févr. 2024 à 00:08, Dan Smith via chirp_devel <<a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> I'm not not an expert, but this is what I do<br>
> <br>
> I checkout a new branch<br>
> <br>
> $ git checkout origin -b test-some-more-drivers<br>
> <br>
> Soon after I make the first changes, I commit them<br>
> <br>
> $ git commit -a<br>
> <br>
> Then as I continue my work, I continue to amend my commit<br>
> <br>
> $ git commit -a --amend<br>
<br>
Yep, this, but be sure to:<br>
<br>
$ git fetch origin<br>
<br>
(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.<br>
<br>
--Dan<br>
_______________________________________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" rel="noreferrer" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br>
</blockquote></div>