Disable automatic check for newer version during install

[Chris Evans]

Hi,

I'm using the MSI to install TortoiseSVN unattended using the /qn option. Is there a way to disable checks for updates during the install? Or even do it after install for all users somehow?

Thanks

*bypass*

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2715688

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Stefan Küng]

On 31.03.2011 19:09, Chris Evans wrote:
> Hi,
>
> I'm using the MSI to install TortoiseSVN unattended using the /qn
> option. Is there a way to disable checks for updates during the
> install? Or even do it after install for all users somehow?

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-admins-upgradecheck.html

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2715785

[Eric Hirst]

Hi,

We do a lot of automated integration testing using large baseline text files. Occasionally a code change will require a single simple change to be applied to hundreds or even thousands of lines in multiple baseline files. We would like to make the review and check-in process for these baseline files more streamlined and less susceptible to "needle-in haystack" errors where we miss a glaring error among many lines of expected changes.

I'm imagining a feature which would support a workflow similar to the following:

1. Open 1-2 Commit dialogs. Your "session" has started.
2. Double-click on an item in the dialogs to start diffing and marking off items for check-in.
3. In TortoiseMerge, notice that there are thousands of similar changes in the files being compared.
4. In TortoiseMerge, expand a _NEW_ regular expression "ignore" window. By default, it might be blank or it might have regular expressions in place corresponding to your current whitespace-ignore preferences. (It might also have regular expressions to match code comments, if an "ignore comments" option were present.)
5. Add a regular expression to the ignore window and refresh. Suddenly you're down to a few hundred changes. Maybe the regex-filtered stuff is still apparent in the GUI, but easily skipped over.
6. Iterate until you are happy, then close* TortoiseMerge.
7. Continue working through the other files in your session, adjusting and tuning your regex filter set as you go.
8. Check in your work to complete your session.

*Being careful not to hit Esc twice... Doh!

That's the basic idea. There's some latitude. The other big use case I see for it is in code refactoring. I would be curious to know if it would be of value to others. I also have a number of thoughts about ways to persist and share regex filter libraries across users, checking default filter sets as text or XML files into SVN folders, for example.

Thanks, Eric

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2715888

[David Huang]

On Mar 31, 2011, at 7:44 PM, Eric Hirst wrote:
> We do a lot of automated integration testing using large baseline text files. Occasionally a code change will require a single simple change to be applied to hundreds or even thousands of lines in multiple baseline files. We would like to make the review and check-in process for these baseline files more streamlined and less susceptible to "needle-in haystack" errors where we miss a glaring error among many lines of expected changes.

Would using a custom diff utility instead of TortoiseMerge work for you? E.g., I think configuring TSVN to use WinMerge <http://winmerge.org/> would let you do what you wanted.

--
Name: Dave Huang | Mammal, mammal / their names are called /
INet: kh...@azeotrope.org | they raise a paw / the bat, the cat /
FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 35 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2715927

[Chris Evans]

Thanks Stefan,

I was hoping to do the equivalent of unticking the option in the GUI so it doesn't check at all. I can see
setting HKEY_CURRENT_USER\Software\TortoiseSVN\CheckNewer to 0 will probably do it on a per user basis. But I'd like to do it for any user without using a logon script or similar to set the registry key. Any ideas? Or is this not possible? Maybe I could request this as a feature for the MSI to be able to set the default user settings?

Thanks

*bypass*

> unsub...@tortoisesvn.tigris.org].

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2715985

[Stefan Küng]

On 01.04.2011 02:44, Eric Hirst wrote:
> Hi,
>
> We do a lot of automated integration testing using large baseline text files. Occasionally a code change will require a single simple change to be applied to hundreds or even thousands of lines in multiple baseline files. We would like to make the review and check-in process for these baseline files more streamlined and less susceptible to "needle-in haystack" errors where we miss a glaring error among many lines of expected changes.
>
> I'm imagining a feature which would support a workflow similar to the following:
>
> 1. Open 1-2 Commit dialogs. Your "session" has started.
> 2. Double-click on an item in the dialogs to start diffing and marking off items for check-in.
> 3. In TortoiseMerge, notice that there are thousands of similar changes in the files being compared.
> 4. In TortoiseMerge, expand a _NEW_ regular expression "ignore" window. By default, it might be blank or it might have regular expressions in place corresponding to your current whitespace-ignore preferences. (It might also have regular expressions to match code comments, if an "ignore comments" option were present.)
> 5. Add a regular expression to the ignore window and refresh. Suddenly you're down to a few hundred changes. Maybe the regex-filtered stuff is still apparent in the GUI, but easily skipped over.
> 6. Iterate until you are happy, then close* TortoiseMerge.
> 7. Continue working through the other files in your session, adjusting and tuning your regex filter set as you go.
> 8. Check in your work to complete your session.
>
> *Being careful not to hit Esc twice... Doh!
>
> That's the basic idea. There's some latitude. The other big use case I see for it is in code refactoring. I would be curious to know if it would be of value to others. I also have a number of thoughts about ways to persist and share regex filter libraries across users, checking default filter sets as text or XML files into SVN folders, for example.

See here:
http://code.google.com/p/tortoisesvn/issues/detail?id=5

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2716263

[Eric Hirst]

Thanks Stefan -- I voted on the code comments feature request.

In practice, I haven't seen much need to exclude code comments. They are easy enough to review manually. But I have seen a lot of cases (refactoring especially) where I've had to turn whitespace and line feed settings on and off during comparison sessions. If custom filters were available, I'd be adding and removing those a lot as well. So I'd lobby for some sort of unified interface for whitespace options, code comments, and custom ignore filters.

If multi-line regex filters for /* */ comments can be made to work, there might be nice opportunities to write other custom multi-line filters to cover common refactoring scenarios. For example, breaking up a long C# argument list into multiple lines. I don't know if anyone has come up with a good solution for this in other tools or not. There are some subtleties here -- reviewers might want to see all changes but also have automated cues to indicate what's cosmetic and what isn't.

User interface could be a simple text editor window (disable/enable filters by commenting/uncommenting lines of text), or something fancier with checkboxes, etc. A full implementation would also support customized defaults based on both file type (to cover the code comment use case) and file location ("I want to filter out tool-generated datetime patterns from XML files in directory \foo...")

-Eric

-----Original Message-----
From: Stefan Küng [mailto:torto...@gmail.com]

See here:
http://code.google.com/p/tortoisesvn/issues/detail?id=5

Stefan

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2716263

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2717722

[Lübbe Onken]

Hi Eric,

I'm using ExamDiff Pro exclusively at work for all my diff actions. It allows some very nice custom filter definitions. Maybe that tool goes into the right direction for you, and maybe Stefan can draw some inspiration for future TMerge enhancements from it :)

Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5

       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control

   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
 

[Eric Hirst]

I've finally started trying to put this to use today, after noticing it appear in the GUI (thanks!) a while ago.

I like the functionality, but have 2 suggestions:

1. I'd like the list of regex filters to be multi-select.

I can work around this with some denormalization, e.g. by creating one filter of the form:

(\<screenTip.*)|(\<description.*)

to filter out <screenTip> and <description> XML nodes in a large baseline file I'm currently reviewing. However, this makes it hard to build a filter library that allows me to mix and match.

2. [gold plating!] I'll probably want to share my filters at some point. For now the workaround is simple enough, since I see they're in a text file: %AppData%\Roaming\TortoiseSVN\regexfilters.ini.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3142109