Tim!
On Wed, Apr 09 2025 at 17:44, Tim Bird wrote:
>> From: Thomas Gleixner
>> On Tue, Apr 08 2025 at 17:34, Tim Bird wrote:
>> And yes, it ignores not yet tracked files, but if you want to check
>> them, then it's easy enough to commit them temporarily or provide a
>> dedicated file target to th
> -Original Message-
> From: Thomas Gleixner
> On Tue, Apr 08 2025 at 17:34, Tim Bird wrote:
> >> -Original Message-
> > For what it's worth, I've always been a bit skeptical of the use of the
> > python git module
> > in spdxcheck.py. Its use makes it impossible to use spdxcheck
On Tue, Apr 08 2025 at 17:34, Tim Bird wrote:
>> -Original Message-
> For what it's worth, I've always been a bit skeptical of the use of the
> python git module
> in spdxcheck.py. Its use makes it impossible to use spdxcheck on a kernel
> source tree
> from a tarball (ie, on source not
Hi Tim
On Tue, 8 Apr 2025 at 20:12, Greg Kroah-Hartman
wrote:
> > Let me know if anyone objects to me working up a refactoring of spdxcheck.py
> > eliminating the use of the python 'git' module, and submitting it for
> > review.
>
> No objection from me!
SGTM. Depending on how much time you ne
> -Original Message-
> From: Gon Solo
> It's a known problem:
> https://github.com/gitpython-developers/GitPython/issues/2003
> https://github.com/python/cpython/issues/118761#issuecomment-2661504264
>
For what it's worth, I've always been a bit skeptical of the use of the python
git mo
On Tue, Apr 08, 2025 at 05:34:20PM +, Bird, Tim wrote:
> > -Original Message-
> > From: Gon Solo
> > It's a known problem:
> > https://github.com/gitpython-developers/GitPython/issues/2003
> > https://github.com/python/cpython/issues/118761#issuecomment-2661504264
> >
>
> For what it
It's a known problem:
https://github.com/gitpython-developers/GitPython/issues/2003
https://github.com/python/cpython/issues/118761#issuecomment-2661504264
> > checkpatch suddenly broke for me with the same error as shown here and the
> > patch fixed it.
> >
> > Tested-by: Duje Mihanović
Turns out, it was not enough; the variable is used later.
How about the following patch?
>From 763f25c8ca2e29f343bfd109a17501de71b38d43 Mon Sep 17 00:00:00 2001
> checkpatch suddenly broke for me with the same error as shown here and the
> patch fixed it.
>
> Tested-by: Duje Mihanović
Same for me.
Tested-by: Andreas Wendleder
On Tuesday, 25 February 2025 14:10:41 Central European Summer Time Ricardo
Ribalda wrote:
> If the git.Repo object's scope extends to the Python interpreter's
> shutdown phase, its destructor may fail due to the interpreter's state.
>
> Exception ignored in:
> Traceback (most recent call last):
On Fri, Apr 04, 2025 at 08:29:21AM +0200, Ricardo Ribalda wrote:
> On Fri, 4 Apr 2025 at 08:22, Greg Kroah-Hartman
> wrote:
> >
> > On Thu, Apr 03, 2025 at 11:34:14PM +0200, Ricardo Ribalda wrote:
> > > Friendly ping
> >
> > Empty pings provide no context at all :(
>
> Do you mean that I'd rather
On Fri, 4 Apr 2025 at 08:22, Greg Kroah-Hartman
wrote:
>
> On Thu, Apr 03, 2025 at 11:34:14PM +0200, Ricardo Ribalda wrote:
> > Friendly ping
>
> Empty pings provide no context at all :(
Do you mean that I'd rather left the whole patch as context, or that I
should provide a reason for the ping?
On Thu, Apr 03, 2025 at 11:34:14PM +0200, Ricardo Ribalda wrote:
> Friendly ping
Empty pings provide no context at all :(
Friendly ping
If the git.Repo object's scope extends to the Python interpreter's
shutdown phase, its destructor may fail due to the interpreter's state.
Exception ignored in:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/git/cmd.py", line 565, in __del__
File "/usr/lib/python3/dis
15 matches
Mail list logo
