Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jan 2024 22:07:56 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Cy Schubert <Cy.Schubert@cschubert.com>
Cc:        Jessica Clarke <jrtc27@freebsd.org>, Jung-uk Kim <jkim@freebsd.org>,  src-committers <src-committers@freebsd.org>,  "<dev-commits-src-all@freebsd.org>" <dev-commits-src-all@freebsd.org>,  "<dev-commits-src-main@freebsd.org>" <dev-commits-src-main@freebsd.org>
Subject:   Re: git: 722b16673c40 - main - acpica: Import ACPICA 20230331
Message-ID:  <CANCZdfr_kWeBKH5bpWRs6XPUQfbikow8MK%2B3edmDVse7j_QsOQ@mail.gmail.com>
In-Reply-To: <20240130205710.11cf19cf@slippy>
References:  <202401310406.40V46AUG000837@gitrepo.freebsd.org> <3BE4D4E2-DFF3-4F68-B3D3-8CE9C27089A5@freebsd.org> <20240130205710.11cf19cf@slippy>

next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000054b556061036dd0f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 30, 2024, 9:57=E2=80=AFPM Cy Schubert <Cy.Schubert@cschubert.co=
m> wrote:

> On Wed, 31 Jan 2024 04:29:18 +0000
> Jessica Clarke <jrtc27@freebsd.org> wrote:
>
> > On 31 Jan 2024, at 04:06, Jung-uk Kim <jkim@FreeBSD.org> wrote:
> > >
> > > The branch main has been updated by jkim:
> > >
> > > URL:
> https://cgit.FreeBSD.org/src/commit/?id=3D722b16673c40aedf280895f2f2f676b=
b494518d7
> > >
> > > commit 722b16673c40aedf280895f2f2f676bb494518d7
> > > Author:     Jung-uk Kim <jkim@FreeBSD.org>
> > > AuthorDate: 2024-01-30 21:43:45 +0000
> > > Commit:     Jung-uk Kim <jkim@FreeBSD.org>
> > > CommitDate: 2024-01-31 03:16:36 +0000
> > >
> > >    acpica: Import ACPICA 20230331
> > >
> > >    (cherry picked from commit
> 8e013e1e3b81740266738226667431cf5c28b17a)
> >
> > Cherry-pick not merge for a vendor merge?..
>
> Probably not Kosher but, a general git question about cherry-picks vs
> merges. A cherry-pick, without the -x but specifying the source branch,
> results in no cherry picked merge but a merge of the last commit of the
> source branch to the current branch.
>
> Can someone explain this? And if this would be any different from a
> merge from a branch that is ahead by one commit since the last merge?
>

This is functionally identical in the resulting tree, except only one
parent is recorded for the commit. If there were no fixups needed, the next
merge would automatically skip the cherry-picked commit due the commit
hashes matching. However if fixups were needed, there may be conflicts on
the next merge in cases I can only hand wave about, but have hit once or
twice. A merge seems to be better because it only looks at changes since
the last common ancestor. I think a merge would handle the need to revert
better, though my experience with awk is making me question that.

Warner

--=20
> Cheers,
> Cy Schubert <Cy.Schubert@cschubert.com>
> FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
> NTP:           <cy@nwtime.org>    Web:  https://nwtime.org
>
>                         e^(i*pi)+1=3D0
>

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

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Tue, Jan 30, 2024, 9:57=E2=80=AFPM Cy Schubert &lt;=
<a href=3D"mailto:Cy.Schubert@cschubert.com">Cy.Schubert@cschubert.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 31 Jan 2024 04:2=
9:18 +0000<br>
Jessica Clarke &lt;<a href=3D"mailto:jrtc27@freebsd.org" target=3D"_blank" =
rel=3D"noreferrer">jrtc27@freebsd.org</a>&gt; wrote:<br>
<br>
&gt; On 31 Jan 2024, at 04:06, Jung-uk Kim &lt;jkim@FreeBSD.org&gt; wrote:<=
br>
&gt; &gt; <br>
&gt; &gt; The branch main has been updated by jkim:<br>
&gt; &gt; <br>
&gt; &gt; URL: <a href=3D"https://cgit.FreeBSD.org/src/commit/?id=3D722b166=
73c40aedf280895f2f2f676bb494518d7" rel=3D"noreferrer noreferrer" target=3D"=
_blank">https://cgit.FreeBSD.org/src/commit/?id=3D722b16673c40aedf280895f2f=
2f676bb494518d7</a><br>
&gt; &gt; <br>
&gt; &gt; commit 722b16673c40aedf280895f2f2f676bb494518d7<br>
&gt; &gt; Author:=C2=A0 =C2=A0 =C2=A0Jung-uk Kim &lt;jkim@FreeBSD.org&gt;<b=
r>
&gt; &gt; AuthorDate: 2024-01-30 21:43:45 +0000<br>
&gt; &gt; Commit:=C2=A0 =C2=A0 =C2=A0Jung-uk Kim &lt;jkim@FreeBSD.org&gt;<b=
r>
&gt; &gt; CommitDate: 2024-01-31 03:16:36 +0000<br>
&gt; &gt; <br>
&gt; &gt;=C2=A0 =C2=A0 acpica: Import ACPICA 20230331<br>
&gt; &gt; <br>
&gt; &gt;=C2=A0 =C2=A0 (cherry picked from commit 8e013e1e3b817402667382266=
67431cf5c28b17a)=C2=A0 <br>
&gt; <br>
&gt; Cherry-pick not merge for a vendor merge?..<br>
<br>
Probably not Kosher but, a general git question about cherry-picks vs<br>
merges. A cherry-pick, without the -x but specifying the source branch,<br>
results in no cherry picked merge but a merge of the last commit of the<br>
source branch to the current branch.<br>
<br>
Can someone explain this? And if this would be any different from a<br>
merge from a branch that is ahead by one commit since the last merge?<br></=
blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">This i=
s functionally identical in the resulting tree, except only one parent is r=
ecorded for the commit. If there were no fixups needed, the next merge woul=
d automatically skip the cherry-picked commit due the commit hashes matchin=
g. However if fixups were needed, there may be conflicts on the next merge =
in cases I can only hand wave about, but have hit once or twice. A merge se=
ems to be better because it only looks at changes since the last common anc=
estor. I think a merge would handle the need to revert better, though my ex=
perience with awk is making me question that.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Warner</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-- <br>
Cheers,<br>
Cy Schubert &lt;<a href=3D"mailto:Cy.Schubert@cschubert.com" target=3D"_bla=
nk" rel=3D"noreferrer">Cy.Schubert@cschubert.com</a>&gt;<br>
FreeBSD UNIX:=C2=A0 &lt;cy@FreeBSD.org&gt;=C2=A0 =C2=A0Web:=C2=A0 <a href=
=3D"https://FreeBSD.org" rel=3D"noreferrer noreferrer" target=3D"_blank">ht=
tps://FreeBSD.org</a><br>
NTP:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:cy@nwtim=
e.org" target=3D"_blank" rel=3D"noreferrer">cy@nwtime.org</a>&gt;=C2=A0 =C2=
=A0 Web:=C2=A0 <a href=3D"https://nwtime.org" rel=3D"noreferrer noreferrer"=
 target=3D"_blank">https://nwtime.org</a><br>;
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 e^(i*pi)+1=3D0<br>
</blockquote></div></div></div>

--00000000000054b556061036dd0f--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr_kWeBKH5bpWRs6XPUQfbikow8MK%2B3edmDVse7j_QsOQ>