Re: on mr 28 run locally.

--===============4486012749743957370==
Content-Type: multipart/alternative; boundary="000000000000bec4e906579aa7c8"

--000000000000bec4e906579aa7c8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 27, 2026 at 12:01=E2=80=AFPM Florent Rougon via Flightgear-deve=
l <
[email protected]> wrote:

> Le 27/07/2026, Patrick Callahan <[email protected]> a =C3=A9crit:
>
> > I wish there was an *easy* process to filter out automatable cosmetic
> > changes
> > from substantive ones into a separate preliminary MR on the affected
> files.
>
> If both sets of changes don't affect the same areas, you can use
> 'git add -p' ('git reset -p' to back off) and commit the first set, then
> deal with the second set (and possibly more). Otherwise, it is indeed
> more complicated...
>

Yeah. I=E2=80=99d want something so simple to use it could be part of a pre=
-commit
process.

 Without that, delay and manual separation after the pre-commit messes
takes too much dev attention.  And that makes it not worth the bother.


> Regards
>
> --
> Florent
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

--000000000000bec4e906579aa7c8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><br></div><div><br><div class=3D"gmail_quote gmail_quote_container"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 27, 2026 at 12:01=E2=80=AFP=
M Florent Rougon via Flightgear-devel &lt;<a href=3D"mailto:flightgear-deve=
[email protected]">[email protected]</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">Le 27/07/2026, Patrick Callahan=
 &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">pat.calla=
[email protected]</a>&gt; a =C3=A9crit:<br>
<br>
&gt; I wish there was an *easy* process to filter out automatable cosmetic<=
br>
&gt; changes<br>
&gt; from substantive ones into a separate preliminary MR on the affected f=
iles.<br>
<br>
If both sets of changes don&#39;t affect the same areas, you can use<br>
&#39;git add -p&#39; (&#39;git reset -p&#39; to back off) and commit the fi=
rst set, then<br>
deal with the second set (and possibly more). Otherwise, it is indeed<br>
more complicated...<br>
</blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">Yeah. I=E2=80=99=
d want something so simple to use it could be part of a pre-commit process.=
=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">=C2=A0Without tha=
t, delay and manual separation after the pre-commit messes takes too much d=
ev attention.=C2=A0 And that makes it not worth the bother.</div><div dir=
=3D"auto"><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Regards<br>
<br>
-- <br>
Florent<br>
<br>
<br>
_______________________________________________<br>
Flightgear-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank"=
>[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/flightgear-devel" r=
el=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/lis=
tinfo/flightgear-devel</a><br>
</blockquote></div></div>

--000000000000bec4e906579aa7c8--


--===============4486012749743957370==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============4486012749743957370==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

--===============4486012749743957370==--