On Feb/28, Peter Palfrader wrote:
> Maybe we should be able to pass the name of the .changes file to
> gen-DSA, and then the script can go and use all the information from
> there?

Implementation-wise, this sounds like a much more sensible approach, but
since the *.changes files may not live on the machine where the advisory
is drafted, I'd still lean toward making this behavior optional.

Cheers,

--Seb

Reply via email to