[pacman-dev] [PATCH] doc/pacman.8.txt: improve description of -Qt

From: Ivy Foster Though correct, the wording of the description of Query's -t/--unrequired option was confusing. Closes FS#48144. Signed-off-by: Ivy Foster --- doc/pacman.8.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff

Re: [pacman-dev] [PATCH v2] makepkg: print filenames and line numbers of references to $srcdir & $pkgdir in built package

We're not very strict about this, but please try to keep the first line of the commit message fairly short, ideally around 50 characters. On 10/14/16 at 08:21pm, ivy.fos...@gmail.com wrote: > From: Ivy Foster > > grep -n output is used to match format of compiler warnings.

Re: [pacman-dev] [PATCH v2] makepkg: print filenames and line numbers of references to $srcdir & $pkgdir in built package

On 14 Oct 2016, at 10:07 pm -0400, Andrew Gregory wrote: > We're not very strict about this, but please try to keep the first > line of the commit message fairly short, ideally around 50 characters. Noted, thanks. > On 10/14/16 at 08:21pm, ivy.fos...@gmail.com wrote: > > From: Ivy Foster

[pacman-dev] [PATCH] makepkg: print filenames and line numbers of references to $srcdir & $pkgdir in built package

From: Ivy Foster grep -n output is used to match format of compiler warnings. Since rewriting build_references() anyway, tweaked quoting. Implements FS#31558. Signed-off-by: Ivy Foster --- scripts/libmakepkg/lint_package/build_references.sh.in | 15

[pacman-dev] [PATCH v2] makepkg: print filenames and line numbers of references to $srcdir & $pkgdir in built package

From: Ivy Foster grep -n output is used to match format of compiler warnings. Since rewriting build_references() anyway, tweaked quoting. Implements FS#31558. Signed-off-by: Ivy Foster --- scripts/libmakepkg/lint_package/build_references.sh.in | 16

[pacman-dev] [PATCH v2] Parametrise the different ways in which the payload is reset

In FS#43434, Downloads which fail and are restarted on a different server will resume and may display a negative download speed. The payload's progress in libalpm was not properly reset which ultimately caused terminal noise because the line width calculation assumes positive download speeds.