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

Re: [TSVN] Trac/bugtraq - Ticket to Changeset link

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-27 22:08:48 CEST

SteveKing <steveking@gmx.ch> wrote on 10/27/2004 03:26:30 PM:

> Mark Phippard wrote:
> > These three are irrelevant. The types of users I envision this for
> > never find another client. Even if they did, I think anyone that
> > on this feature would try to also have some kind of pre-commit hook.
> > is mainly about making the front-end friendlier.
> See, that's exactly why I think I should rather just delete your mails
> instead of answering them: you just think about _your_ users. But TSVN
> has many users, and I have to think about them too.

I hope this was somewhat tongue in cheek? I am on your side, I am just
trying to explore the issue. I think I used poor wording and apologize.

My point was that the overwhelming majority of those TSVN users you
describe would never run into this parm, the ones that do would be ones
where someone decided they needed it. In those scenarios, I believe that
the "user" would have had TSVN installed by their IT, and they would not
know to complain to anyone else, let alone look for an alternative client.
 That is what I meant by "irrelevant".

> And what's your
> point anyway if a pre-commit hook does some checks too?
> I mean a warning (as I suggested) would be enough. If then the
> pre-commit hook rejects the commit - at least the user was warned about
> that. But at least the user wasn't _forced_ to choose some bug-ID which
> maybe has nothing to do with the commit.

If the user is warned but can override it, but then a hook stops it, how
did that help? Especially if it took a long time to send the commit to
the server. As I said, I wouldn't expect stopping the user to be the
default, but it seems like a reasonable option to enable.

> >
> >
> > These are your opinions spilling through. If you have to undergo SOX
> > audits or are trying to maintain an ITIL certification, then yes you
> > want to have a bug-ID for these changes.
> Don't know what SOX audits or ITIL certifications are. But if they're
> similar to some other certifications we have here for companies then I
> can guarantee you one thing for sure: you can smoke those
> certifications!

Who cares if they are bogus? If you work in an audited industry you have
no choice but comply. I am not suggesting that anyone WANTS to have to
undergo these audits. They have just become a fact of life.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 23:17:52 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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