On Fri, 24 Jan 2025 10:51:03 +0100 Andreas Grünbacher <agr...@gnu.org> wrote:
> Am Fr., 24. Jan. 2025 um 09:54 Uhr schrieb Greg KH <g...@kroah.com>: > > On Fri, Jan 24, 2025 at 09:37:46AM +0100, Petr Tesarik via Quilt-dev wrote: > > > > > Hi all, > > > > > > following a recent SUSE-internal discussion about differences between > > > patches produced by Git and patches produced by GNU diff, I wonder if > > > we could allow git-diff as an alternative backend in quilt. > > > > > > FWIW I am willing to send in patches, but I want to make sure they > > > would be appreciated before I invest my time. > > I assume you mean "git diff" as well as "git apply". Supporting those > would certainly help; it would probably give quilt full binary diff > support "for free". But that won't be easy to achieve: quilt relies on > GNU patch to create backup files when applying patches, and it's those > backup files that "quilt diff" and similar commands operate against. To be honest, I had only "git diff" in mind. It does not bring much (no support for binary patches), but it does at least provide longer function names in hunk headers and some differences in context matching, which is relevant in a few corner cases. But now that you mention it, "git apply" may bring much more value. > In addition, the last time I checked, "git apply" had weird heuristics > built in instead of accepting a specific strip level; see GNU patch's > -p / --strip option. Quilt remembers the strip levels of patches and > preserves strip levels 0 and 1 when refreshing patches. Thanks for some pointers. I'll see how much functionality is missing in git-apply and whether it's feasible to add it. Petr T _______________________________________________ Quilt-dev mailing list Quilt-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/quilt-dev
