Hi,
On Tue, Sep 20, 2022 at 10:56:05AM -0400, Antoine Beaupré wrote:
https://github.com/git-multimail/git-multimail/issues/221#issuecomment-1245009306
(To avoid bring noisy for upstream, i just recorded it in a issue)
I don't think pull requests are noisy... you should probably just submit
this
On 2022-09-22 17:03:24, Bo YU wrote:
> Hi,
> On Tue, Sep 20, 2022 at 10:56:05AM -0400, Antoine Beaupré wrote:
>>> https://github.com/git-multimail/git-multimail/issues/221#issuecomment-1245009306
>>> (To avoid bring noisy for upstream, i just recorded it in a issue)
>>
>>I don't think pull requests
On Thu, 22 Sep 2022 12:35:12 -0400
Antoine Beaupré wrote:
> I think the simplest solution is not to rewrite the launcher, but to
> rename it. So in debian/rules, you would simply do:
>
> override_dh_auto_install:
> dh_auto_install
> mv debian/git-multimail/usr/bin/git_multimail.p
On 2022-09-22 19:43:24, Jeroen Ploemen wrote:
> On Thu, 22 Sep 2022 12:35:12 -0400
> Antoine Beaupré wrote:
>
>> I think the simplest solution is not to rewrite the launcher, but to
>> rename it. So in debian/rules, you would simply do:
>>
>> override_dh_auto_install:
>> dh_auto_install
>
Emanuele Rocca writes:
> What's wrong with pushing your work before uploading to ftp-master
> instead? :-)
I am learning to do this with my packages.
Because otherwise, when I push to get, I often find I forgot to do a
pull beforehand, and there are changes in salsa that are not reflected
in my
> Well but that's the whole point of automated testing. There's no *need*
> to do it locally if it's already done by Salsa for you. What is already
> automated and working pretty well is:
>
> - amd64 build
> - i386 build
> - source build
> - autopkgtest
> - blhc
> - lintian
> - piuparts
> - reprote
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "domdf-python-tools":
* Package name : domdf-python-tools
Version : 3.4.0-1
Upstream contact : Dominic Davis-Foster
* URL : https://github.com/domdfcoding/d
Hello Emanuele,
Am 21.09.22 um 12:01 schrieb Emanuele Rocca:
Well but that's the whole point of automated testing. There's no *need*
to do it locally if it's already done by Salsa for you. What is already
automated and working pretty well is:
- amd64 build
- i386 build
- source build
- autopkgt
Hi Carsten (2022.09.23_05:01:05_+)
> sure, that's a killer argument that I can't really argue against. But that
> is not the point for me.
>
> For all these checks we already have existing infrastructure, running the
> same also by a pipeline job isn't helping at all if it's not clear how to
>
Hi Carsten, Hi List,
Le Fri, Sep 23, 2022 at 07:01:05AM +0200, Carsten Schoenert a écrit :
> heavily force pushing to not blow up the git tree with dozens of Fixup
> commits! In the 'official' git tree this is a no go of course.
Would doing the work in a git branch and 'git merge --squash' at the
10 matches
Mail list logo
