On Thu, Apr 24, 2008 at 9:55 AM, Mark Combellack <[EMAIL PROTECTED]> wrote:
<snip> * Typically, users do not do an SVN checkout of the source code and > will not have SVN installed. They are typically provided with a jar file > containing the source code. They will not be able to run SVN command to > work > out which versions of source code they are running > > * Typically, there are many, many more users than there are > developers > > * If a source file is printed out or attached as an email as part > of > a bug report or published on a web server, the source code will contain the > SVN revision number. This makes the bug easier to fix as you know the > revision number. The SVN commands will not be able to tell you the revision > number in these scenarios. > >From what everyone has said so far the above seem like the only real justification for where these might be useful, and I'm sceptical whether users really would care or use these as from what i've seen they say things like "it broke in 1.1" or "it worked last week" and don't go down to mentioning individual class files let alone revisions of the file, and usually don't post whole class files to bug reports. Anyway, I'm obviously in a minority on this so if everyone else really really wants to add these i wont get in the way. How would that work - it would be manditory to add them to each new file and everyone must have their SVN client configured so the correct SVN properties get set? ...ant
