On Sat, Oct 24, 2009 at 8:55 PM, Sune Foldager <sune.folda...@me.com> wrote: > I need to call hgtk log with -R bundle:<some bundle> (the feature from my > other patch), and I > need it to fork. Normally it does so, but when -R is used, it doesn't by > design. I am not sure > why this is the case (a particular usage scenario) or why --nofork can't just > be used when needed, > but if it's something we want to keep (i.e. -R implies --nofork), I need a > way to force hgtk > to fork anyway; hence, this patch. > > I don't need it if the -R => --nofork implication is removed, but I assume > it's there for a > good reason :)
The reason -R implies no fork is that hgtk must chdir() into the repository root when it runs (all the dialogs assume they are running inside the current repository). If a user tries to launch hgtk from a relative path, hgtk will not be able to fork safely after the chdir. It's non-optimal, but that's why it's there. -- Steve Borho ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
