Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Aug 2022 09:54:37 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Nuno Teixeira <eduardo@freebsd.org>
Cc:        freebsd-git <freebsd-git@freebsd.org>
Subject:   Re: git wants to commit more files than expected ?
Message-ID:  <CANCZdfpEvQEbaxoDXfqN7kPzwH9dsZFiTx2ajBtw4XU2p8oJNw@mail.gmail.com>
In-Reply-To: <CAFDf7U%2BQCPu%2BYCHqfJ%2BhmvgiX2j=W0qRRjCvnxbdmPns=fN37g@mail.gmail.com>
References:  <Yvd0ziIpQpZTjVyd@fc.opsec.eu> <99af6a44013b44d7ec1196bc3809e3aa@FreeBSD.org> <YvfC8Inx6FtrlaT6@fc.opsec.eu> <CAFDf7U%2BQCPu%2BYCHqfJ%2BhmvgiX2j=W0qRRjCvnxbdmPns=fN37g@mail.gmail.com>

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

On Sat, Aug 13, 2022 at 9:45 AM Nuno Teixeira <eduardo@freebsd.org> wrote:

> Hi,
>
> I always forgot to use `git commit --amend` when commit needed some
> correction/change. I usually do a `git reset --hard ^HEAD` and then commi=
t
> from scratch :)
>
> Next commit I do I will use amend and see if I got similar problem like
> yours.
>

git rebase -i freebsd/main main

is what I do when I'm working on main and need to 'curate' the commits.

Warner


> Cheers,
>
> Kurt Jaeger <pi@freebsd.org> escreveu no dia s=C3=A1bado, 13/08/2022 =C3=
=A0(s)
> 16:27:
>
>> Hi!
>>
>> > > But if I run a git commit, additional two files turn up:
>> > >
>> > > # Changes to be committed:
>> > > #       modified:   archivers/py-borgbackup/Makefile
>> > > #       new file:   archivers/py-borgbackup/files/patch-setup.py
>> > > #       modified:   print/pdf-tools/Makefile
>> > > #       modified:   print/pdf-tools/distinfo
>> > >
>> > > Why isn't git status not reporting the two pdf-tools files,
>> > > but git commit is ?
>> >
>> > Could you share the 'git commit' command-line that you're using ?
>>
>> It was this:
>>
>> git commit --amend --author=3D'Jose G. Juanino <jjuanino@gmail.com>'
>> archivers/py-borgbackup
>>
>> > If I've to guess then you're probably including the '-a' switch of git
>> > commit. If yes, then please don't include it.
>>
>> I now tried this:
>>
>> git commit --author=3D'Jose G. Juanino <jjuanino@gmail.com>'
>> archivers/py-borgbackup
>>
>> and it worked! Thanks!
>>
>> --
>> pi@FreeBSD.org         +49 171 3101372                  Now what ?
>>
>>
>
> --
> Nuno Teixeira
> FreeBSD Committer (ports)
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Aug 13, 2022 at 9:45 AM Nuno =
Teixeira &lt;<a href=3D"mailto:eduardo@freebsd.org">eduardo@freebsd.org</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr"><div>Hi,</div><div><br></div><div>I always forgot to use `git =
commit --amend` when commit needed some correction/change. I usually do a `=
git reset --hard ^HEAD` and then commit from scratch :)</div><div><br></div=
><div>Next commit I do I will use amend and see if I got similar problem li=
ke yours.<br></div></div></blockquote><div><br></div><div>git rebase -i fre=
ebsd/main main</div><div><br></div><div>is what I do when I&#39;m working o=
n main and need to &#39;curate&#39; the commits.</div><div><br></div><div>W=
arner</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr"><div></div><div>Cheers,<br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Kurt Jaeger &lt;<a h=
ref=3D"mailto:pi@freebsd.org" target=3D"_blank">pi@freebsd.org</a>&gt; escr=
eveu no dia s=C3=A1bado, 13/08/2022 =C3=A0(s) 16:27:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">Hi!<br>
<br>
&gt; &gt; But if I run a git commit, additional two files turn up:<br>
&gt; &gt; <br>
&gt; &gt; # Changes to be committed:<br>
&gt; &gt; #=C2=A0 =C2=A0 =C2=A0 =C2=A0modified:=C2=A0 =C2=A0archivers/py-bo=
rgbackup/Makefile<br>
&gt; &gt; #=C2=A0 =C2=A0 =C2=A0 =C2=A0new file:=C2=A0 =C2=A0archivers/py-bo=
rgbackup/files/patch-setup.py<br>
&gt; &gt; #=C2=A0 =C2=A0 =C2=A0 =C2=A0modified:=C2=A0 =C2=A0print/pdf-tools=
/Makefile<br>
&gt; &gt; #=C2=A0 =C2=A0 =C2=A0 =C2=A0modified:=C2=A0 =C2=A0print/pdf-tools=
/distinfo<br>
&gt; &gt; <br>
&gt; &gt; Why isn&#39;t git status not reporting the two pdf-tools files,<b=
r>
&gt; &gt; but git commit is ?<br>
&gt; <br>
&gt; Could you share the &#39;git commit&#39; command-line that you&#39;re =
using ?<br>
<br>
It was this:<br>
<br>
git commit --amend --author=3D&#39;Jose G. Juanino &lt;<a href=3D"mailto:jj=
uanino@gmail.com" target=3D"_blank">jjuanino@gmail.com</a>&gt;&#39; archive=
rs/py-borgbackup<br>
<br>
&gt; If I&#39;ve to guess then you&#39;re probably including the &#39;-a&#3=
9; switch of git <br>
&gt; commit. If yes, then please don&#39;t include it.<br>
<br>
I now tried this:<br>
<br>
git commit --author=3D&#39;Jose G. Juanino &lt;<a href=3D"mailto:jjuanino@g=
mail.com" target=3D"_blank">jjuanino@gmail.com</a>&gt;&#39; archivers/py-bo=
rgbackup<br>
<br>
and it worked! Thanks!<br>
<br>
-- <br>
pi@FreeBSD.org=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+49 171 3101372=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now what ?<br>
<br>
</blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr"><div dir=
=3D"ltr"><span style=3D"color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Co=
mmitter (ports)</span></div></div>
</blockquote></div></div>

--00000000000015f38105e6216b92--



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