Eric J. Smith wrote:
> It seems like we are miscommunicating a bit. What I am talking about is
> leaving everything the same for issue tracking as it is now except the
> actual affected issue numbers that are currently stored in the revision
> comment and parsed out in the show log dialog. You would still store the
> exact same folder properties (bugtraq:*) to turn the issue tracking feature
> on and off, but you would store the actual affected issues in a revision
> property instead of in the revision log message.
Ah, now I see.
Yes, for that the revision property could be used.
> Correct me if I'm wrong, but wouldn't the only place that you would need to
> look the affected issues information up and possibly show it be in the show
> log window? And when you are in the show log window you know exactly which
> revision to check for the properties.
Yes, if the normal folder properties are still in use.
> That's why I'm confused. You already determine if the issue number box
> should be displayed or not based on the current folder properties. I'm not
> suggesting that you should change this. I think the folder properties work
That was a misunderstanding. I thought you wanted to replace the folder
> What I was suggesting is to store the affected issues list for each revision
> differently. I just think it's a shame to store the affected issues in the
> log message and parse it out and to not take advantage of the property
> system that Subversion provides. So I'm simply suggesting that this
> information be stored with each revision as a "bugtraq:affectedissues"
> property and that the show log dialog be changed to read the information
> from this property instead of parsing the comment.
> I realize that this may not be feasible, but I'm just trying to make sure we
> are talking about the same thing before I give up. :-)
That would be great if the revision properties could be fetched in the
same step as the log messages. And if the commit would set these
properties too in the same step as the actual commit.
But as long as Subversion doesn't provide this, I don't want to
Think about it: if you show the logs, and for every log entry you select
to show, TSVN would have to contact the repository first: this would
slow down the log dialog a lot. Not everyone has the repository
accessible via a LAN - many access the repository over a very slow
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Sep 11 20:15:37 2004