*Background:*

We often need to review old code changes, but only have an old revision
number without knowing the branch. Tortoise SVN doesn’t expose a good way
to look up a specific revision. The only way I know to do it is by opening
the Repo Browser and doing a Show Log on the repo’s root folder, but
changing the revision in the Log window can take a really, really long time
in a repo with 1.7 million commits. (It seems like it’s doing a log from
HEAD, even though you entered an old start revision.) If you set the old
revision in the Repo Browser first, then doing a log of the root folder is
fast, but this process involves a lot of steps and isn’t intuitive.


*The feature:*


This patch file adds a “Show log of repo at revision…” command to the
Explorer context menu. Selecting it on any SVN-controlled file or folder
will show a dialog asking for a revision number, then show the log starting
at that revision. It always shows the log of the root folder, ignoring the
specific file(s) or folder(s) that were selected in Explorer.


*Questions for reviewing the patch:*

   - Where should it go in the context menu? I put it at the end of the
   section with “Show log”, after “Revision graph” for now.
   - Should it be added to any other context menus?
   - I used the same YesNoPair filters as ShellMenuLog. Are those
   appropriate?
   - I added a new L"tsvn_logext" MenuInfo::verb string for this command,
   but I’m not sure what that’s used for.
   - Is svn.GetRepositoryRoot(cmdLinePath) the right way to get the root
   path from an arbitrary path passed on the command line?


Thanks!


Dave Lawrence

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tortoisesvn+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/CADN%2BUxxUTmwj7ZXoUv-opVsa%2Bm2zDPkCWdReUDpU1qASu642ag%40mail.gmail.com.

Attachment: LogAtRevision.patch
Description: Binary data

Reply via email to