Lucas Nussbaum <[email protected]> writes: > I'm not sure that we need Git-Tag-Info (for non-tag2upload packages), as > it sounds easy enough to just guess what is the tag to follow.
If you do end up finding a purpose for an additional field, don't hesitate to propose one. My personal bias here is that I think it may make more sense to have multiple fields with specific and well-defined meanings than to attempt to generalize a specification for one field that can address multiple workflows with significantly different semantics, but I'm open to being convinced that I'm wrong. -- Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
