[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Blame/annotate not good enough...

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Tue, 23 Apr 2013 16:29:15 +0200

Guten Tag Charles Gallo,
am Dienstag, 23. April 2013 um 14:22 schrieben Sie:

> Blame/annotate does exactly what I want, but the client (mumble
> mumble) wants the info in the actual source code file as comments! I
> explained that all the info is in blame/SVN, but they actually said
> "the auditors won't see the repository, just the source, and they
> want to be able to see what changed and by whom". That's why I'm not
> allowed to delete code, only comment out. Sigh

Maybe you should try a different approach: Why do the auditors don't
have or want access to the repo? May read-only copy of the repo to
access offline a solution? If the auditors just need the info about
who changed what as inline comments in the source, because they aren't
allowed to access the repo or else devil himself will kill the world
;-), how about a process generating what they need as an on demand
process? They need access to the code somehow in any way, maybe you
could create the view your client wants as a part of some export or
preparation process using the source code repo you seem to have access
to? You could even build some nice little GUI especially for the
auditors if your client pays well and in time. ;-)

Focusing on specially formatted commits or stuff like that may not be
the only solution.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2013-04-23 16:29:51 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.