[1797] in Kerberos_V5_Development
Re: Conventions for gnats PR tracking
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Thu Sep 26 16:48:42 1996
Date: Thu, 26 Sep 1996 16:48:37 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: raeburn@cygnus.com
Cc: krbdev@MIT.EDU
In-Reply-To: <tx1buet81j2.fsf@cygnus.com> (message from Ken Raeburn on 26 Sep
1996 16:27:45 -0400)
> Fri Sep 20 16:52:07 1996 Barry Jaspan <bjaspan@mit.edu>
>
> * [krb5-admin/1234] configure.in: add unit-test directory
Any given PR number is only used in one category at any given time.
And it is possible to change the category of a PR. I'd suggest
leaving the category out.
<shrug> The reason I like [cat/#] is that it is easy to grep for
(visually and regexp-ly), and it is a nice compact notation that is
gramatically flexible (ie: "this fixes [krb5-lib/1234] which ...").
As for the category, it can change, but it often doesn't, and even if
it does the number stays valid; besides, if it is going to change it
usually has by the time it is being closed. But in the common case
when the category is right, it coveys some (minimally) useful
information (ie: the difference between [krb5-doc/1234] and
[krb5-admin/1234] tells you something that [PR 1234] does not). But
really it does not matter much, as long as the information is there;
any format is better than none.
I'd rather see the PR info at the end or otherwise not in the way of
skimming the standard changelog entries in their usual format.
Sounds fine to me.
I don't think either approach is necessarily wrong. And you can't
insist on a specific way of doing it without implicitly declaring
other ways as wrong.
Sure you can; or, more accurately, you don't have to insist. "Do it
this way, unless you have a good reason not to." That way all the
typical common cases get done one way, instead of N ways for N
developers, and the unusual cases get done however they need to get
done.
Barry
