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?
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?
When I push commits to repos in debian without gbp, it leads to commits going with non d.o address.I have a git setup here where the committer address is set based on the directory I?m under.
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.
Hi,That's allowed, we don't have any rules about this.
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?
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?
When I push commits to repos in debian without gbp, it leads toA while ago, I found that you can add this to ~/.gitconfig:
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.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 119:29:21 |
| Calls: | 125 |
| Calls today: | 125 |
| Files: | 489 |
| D/L today: |
859 files (365M bytes) |
| Messages: | 76,550 |
| Posted today: | 26 |