Re: Is usage of debian email address appropriate while contributing to other free software projects?
Sean Whitton <[email protected]> Sun, 08 Feb 2026 12:55:51 +0000
| Newsgroups | gmane.linux.debian.devel.project |
|---|---|
| Message-ID | <[email protected]> |
Hello, Nilesh Patra [08/Feb 10:10am +0530] wrote: > Hi, > > While pushing commits to debian packages, I have my @d.o configured in global gbp.conf and hence > that address applies to my commits to packaging contributions. However, I have another non @d.o > address in gitconfig. > > When I push commits to repos in debian without gbp, it leads to commits going with non d.o address. > Furthermore, I have to double think if I should use my @d.o when I am forwarding debian > patches to upstream projects v/s when I am not. > > All of this is adding to some confusion and more often than not leading to commits with a mix > of addresses. I don't see any guideline for usage of debian address. Hence, I'd like to ask > is it fine to use @d.o address for all and any free software related work including address > on commits and even communicating on (other) mailing lists? That's allowed, we don't have any rules about this. -- Sean Whitton
signature.asc
(application/pgp-signature, 869 B)
-----BEGIN PGP SIGNATURE----- iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmmIh9cZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQAzxD/46XwB7aIxEzKsNdEG/dsNX hKrtkpXhNedxG5vnUqFp4EbM92Hu/b/ND0+m/8jwhHGZpGXUnV3BKNZ1mcqWj3uJ G6nBoAn+dk0T/cAwN03W3+Ye2cOfMA8iN+t3dp/F8QHbaW/bv+/1/PmUsdy31Geh FMANavaQWmR316LDaTXcnvx0OgGCPyhJ+aYxRjIdyb5bZq243AwUnlM8tFd4DlRf RA8jwQkJcEn7mU+MdxJHcDgtbEr5iPJIlqgqq/ZPRL3pZoYNMNhg7j7Q4x1uyQ9h /WPAUpHfM6779ud2oGvzeikLK2QGRWoeGDMpxQU+KShCfRdmBwMMNh4qNyOvXjra hT4BHEI59PGZYg4fMH5z8VFId1JWdlp+kgZdtsg77YNLbptDSKLpAYbOGgnTdZuK vCREd8PGvggFu5Rw/nc1Re50EgNJf4udx3bIvfpPfoG2w8Saqle8gsRGwbWzLS9H Dj4buXywcLT4ciTRbT7Kg/XryohLSxSla0tjt0BQAy9ARIW1urCS/ZGUxBkhK7gY LHIsZjq3CginSUphyyv3sy55pQUBFutyIDE49Bs/qCMvbH6JTsXaFJLnUFwcuu6s vrrVGCG+yU7TsnXSgmSe6x9OXtdS7qWiwoGrZqKfaV/z05Gq5vGwaFGIWuzC+WDv CuyQW0nORjVk/7jQ6ykraA== =bDh3 -----END PGP SIGNATURE-----