StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Since you mention <code>tf history</code> command, I assume you want to collect/parse logs on the project's (and its files) history of checkins.</p> <p>So in addition to large repository, you also need a good amount of history, am I right? If yes, then here's your set of problems:</p> <ul> <li>Most projects on codeplex use Mercurial, not TFS. So even if you get access, you cannot use TFS with them.</li> <li>As you mentioned, they require you to a be a member for you to access the source.</li> <li>Even if you get access or find a public server (unlikely), you still would need good amount of history.</li> </ul> <p>If I'm correct in my assumptions so far, here's the easiest (bit tedious though) way out:</p> <ul> <li>Go to any large projects's such as <a href="http://nuget.codeplex.com/SourceControl/list/changesets" rel="nofollow">Nuget</a> or <a href="http://wix.codeplex.com/SourceControl/list/changesets" rel="nofollow">Wix</a> revisions </li> <li>Download any old revision (go back as far as you want the history for). You can download zipped src files without being a member.</li> <li>In your test server, checkin the code (<code>src</code>) to create the baseline.</li> <li>Download the next revision.</li> <li>Checkout files in your server and overwrite them with the newer revision's files.</li> <li>While checkin, use the <code>history.txt</code> (<a href="http://wix.codeplex.com/SourceControl/changeset/view/ea1692c2762d#history.txt" rel="nofollow">sample</a>) to create checkin comments</li> <li>Repeat this process few times.</li> </ul> <p>Voila!! You now have a large repository with lot of history! </p> <p>Hope this helps.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload