Ananthu C V <[email protected]> writes: > Hi, > > Doing a 'git add -A' when there's so much random stuff out there is > not good to begin with. And there's always the option of running > debclean before doing that; ie if the clean target knows about > them. In any case, for building twice cases, the artifacts have to be > cleaned up or it'll just cause an ftbfs. So being distracted by them > and adding them to clean target properly is better than forgetting > about them by putting them in gitignore. That's what I think anyway, > YMMV.
I think source package reproducibility and tag2upload-compatibility is more important than helping maintainers who accidentally would do 'git add -A'. /Simon > On 4 June 2026 16:26:45 UTC, Guillem Jover <[email protected]> wrote: >>The problem is that if you do >>the equivalent of something like: >> >> $ debcheckout -a golang-foo >> $ cd golang-foo >> $ dpkg-buildpackage --build=binary >> $ git status >> >>That shows lots of untracked files, which can easily end up being >>committed into git by say «git add -A», and are in general distracting. >> >>Thanks, >>Guillem >>
signature.asc
Description: PGP signature
