Lars Klose wrote:
> Me neither. But I'd expect either there is something similar to the IE
> control (in which case there's no problem) or it must be implemented in
> that svn client itself (in which case the password prompt can be
> implemented right there).
Implementing this directly in Subversion won't happen.
- Subversion uses DAV, not pure http. So it would need a separate lib to
- The bugtracking part is not tied to the repository, it is independent
of that and therefore there's no 'direct' connection between them.
>> - Issue/ticket number
>> - title/subject of the ticken
>> - URL to the ticket, if more information is needed.
>> But not more. For more, the URL and the browser should be used and not
>> a Subversion client.
> True. IMHO the URL is not necessarily needed (but nice anyway) since the
> user supposedly knows where to find his issue tracking system anyway.
I think the URL is needed for one reason:
there will be (believe me, there _will_ be) requests to add more
information, and each user will want "just that information". To prevent
changing the definitions and every client out there every two weeks the
URL is needed. That way you can just tell: click on the link and you
have the information there.
> More fantasizing: If we had the URL on commit, it could even be stored
> as a revision property. But: this would actually be a server side job
> (through some hook) not the svn client's. BTW: That's what I was trying
> with the ticket number lately - didn't have time to finish my
> experiments though :-(
> Later on, if that revision property was in place, TSVN could provide a
> link e.g. from that revision's log entry which opens the browser with
> the ticket URL!
Ok. Please, please read the document here:
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Oct 27 19:07:44 2004