Re: gitk feature request..

From: Pierre Dumuid <pierre.dumuid@adelaide.edu.au>
Date: Nov 8, 2006, 00:06 UTC
Message-ID: <45511F8C.1060705@adelaide.edu.au>
In-Reply-To: <7vslgu28do.fsf@assigned-by-dhcp.cox.net>

> Having said that, is the gitk view supposed to be shared across
> users of a single repository?
>

Show 7 quoted lines

> If you imagine yourself logging into kernel.org (perhaps X
> forwarded over ssh to your local machine) and browsing
> /pub/scm/git/git.git/, the repository itself would not be
> writable by you.  Even if it were, I do not think you would want
> me to reuse the view you used from there next time I did the
> same on the same repository.
>

I've mainly been thinking about users at a home who clone / update a remote repository and work in that repository for themselves. The idea of sshing into another machine seems to me not how git is designed to be used..

Also when one clones, I thought it cloned only the git repository, and not the files for the porcelaines. (an example being the branches directory)

Show 5 quoted lines

> It might make sense to give --state=dir/ parameter to gitk and
> tell it to use that directory to keep persistent data.  Also I
> seem to recall you already have one file under $HOME/ to make
> window geometry or something persistent.
>

I use gitk a lot, and I'd rather not have to specify a command line option all the time, but an override from using the settings in the another directory would be fine..

begin:vcard fn:Pierre Dumuid n:Dumuid;Pierre org:The University of Adelaide;Mechanical Engineering adr:;;;Adelaide;South Australia;5005;Australia email;internet:pierre.dumuid@adelaide.edu.au title:Postgraduate Student tel;work:8303 3847 tel;home:8388 5727 tel;cell:0407570263 note:CRICOS Provider Number 00123M x-mozilla-html:TRUE url:http://www.adelaide.edu.au version:2.1 end:vcard