Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537

2018-08-16 Thread Ricardo Wurmus
Hi Nils, > Ricardo Wurmus transcribed 227 bytes: >> >> Nils Gillmann writes: >> >> > This commit is okay, but let's all please refrain from doing future >> > corrections like this. >> >> Why? >> >> I prefer consistency, so I’m happy with Tobias’s change. […] > Because we also allowed more than

Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537

2018-08-16 Thread Nils Gillmann
Ricardo Wurmus transcribed 1.1K bytes: > > Hi Nils, > > > Ricardo Wurmus transcribed 227 bytes: > >> > >> Nils Gillmann writes: > >> > >> > This commit is okay, but let's all please refrain from doing future > >> > corrections like this. > >> > >> Why? > >> > >> I prefer consistency, so I’m happ

Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537

2018-08-16 Thread Nils Gillmann
Ricardo Wurmus transcribed 227 bytes: > > Nils Gillmann writes: > > > This commit is okay, but let's all please refrain from doing future > > corrections like this. > > Why? > > I prefer consistency, so I’m happy with Tobias’s change. > > -- > Ricardo > Because we also allowed more than on

Re: Closing issues from commits

2018-08-16 Thread Marius Bakke
Marius Bakke writes: > Hello, > > It would be convenient (for me, at least) to have a server-side git hook > that can close debbugs issues. It would grep the commit message for > '^Fixes: ' and automatically send an > email to cont...@debbugs.gnu.org with the mess

Closing issues from commits

2018-08-16 Thread Marius Bakke
Hello, It would be convenient (for me, at least) to have a server-side git hook that can close debbugs issues. It would grep the commit message for '^Fixes: ' and automatically send an email to cont...@debbugs.gnu.org with the message 'close $1 $commit_id'. Is thi

Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537

2018-08-16 Thread Ricardo Wurmus
Nils Gillmann writes: > This commit is okay, but let's all please refrain from doing future > corrections like this. Why? I prefer consistency, so I’m happy with Tobias’s change. -- Ricardo

commit 70f57ae00525f6fc919f62aea647a33b29d28537

2018-08-16 Thread Nils Gillmann
Hi, may I ask why you made commit 70f57ae00525f6fc919f62aea647a33b29d28537? In John's case, okay no (C) or © was present. But no one dictates in any guidelines which writing is correct. I chose (C) some time ago because sometimes I use editors without unicode support. Both writings are correct.