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

RE: Commit Groups

From: Josha Foust <jfoust_at_mankowindows.com>
Date: 2005-12-05 16:42:42 CET

> -----Original Message-----
> From: Aniruddha Apte [mailto:aniapte@gmail.com]
> Sent: Monday, December 05, 2005 7:18 AM
> To: dev@tortoisesvn.tigris.org
> Subject: Re: Commit Groups (was: Working with Changesets in TortoiseSVN.
> New dialog.)
> > Your TortoiseProc.exe seems to be built against r4885 and linked against
> > 'OpenSSL 0.9.7g 11 Apr 2005'. I am using the nightly r5050 which is
> > using 'OpenSSL 0.9.8 05 Jul 2005'. So either I need to downgrade or you
> > need to upgrade. :)
> I've uploaded a TortoiseProc.exe linked against OpenSSL 0.9.8 05 Jul
> 2005. Get it from here:
> http://tortoisesvn.tigris.org/files/documents/406/28400/TortoiseProc.exe

Thanks. It is working for me now.
> > I would also like to be able to rename Group# to something else. It
> > wouldn't have to be very long (15 characters or less). I find myself
> > keeping the log message short so that I can have an easy way to identify
> the
> > commit group.
> Could you suggest a UI for the group name? Should it be numbered or
> not? Something like this? :
> #1[Group Name][Log Message]
> ...
> #2[Group Name][Log Message]

I don't personally see the need for them. As long as they remain in the
same order it should be fine. Reordering them might be useful, so I'm not
sure if you would want to display the numbers... However, I imagine you
would still want some kind of automatic numbering for people that wouldn't
rename the groups (but then they might not reorder them either). Some help
I am, huh?

> regards,
> aniruddha

Josha Foust

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 5 16:45:35 2005

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.