Guido Günther
Guido Günther
Thanks ore spelling out the details. If we make `import-orig` smart enough a separate `gbp prstine-lfs` sounds more useful than somehow folding this into `gbp pristine-tar`. The only bit missing...
Thanks for a having a look! While for the export-orig case (a) this makes sense but I think for the pkg-go use case (b) it's different: There are no tarballs...
For pkg-go I'd simply create the appropriate commit with the files filtered out (with the original commi as parent) and tag it correctly, the rest will then be handled by...
We can focus on creating the filtered commit plus tag first. The dfsg-clean branch is than just an additional parent we add to the commit.
See https://github.com/agx/git-buildpackage/pull/86#issuecomment-1138357289
Hi, thanks for the patches! * patch 3 and 4 could move into a separate PR since they're good to go (Have to think about the --edit case a bit...
See https://github.com/swaywm/wlroots/pull/724
In order to superseed these we should use a format in xdg-output.description that allow to extract that information.
> Why would this be needed? The current description (e.g. `Dell Inc. DELL U2717D J0XYN71G742L (HDMI-A-1)`) is a bit too verbose to present to the user so being able to...
What workarounds do you refer to?