All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Dumuid <pierre.dumuid@adelaide.edu.au>
To: Junio C Hamano <junkio@cox.net>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: gitk feature request..
Date: Wed, 08 Nov 2006 10:36:36 +1030	[thread overview]
Message-ID: <45511F8C.1060705@adelaide.edu.au> (raw)
In-Reply-To: <7vslgu28do.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]


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

> 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)
> 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..


[-- Attachment #2: pierre.dumuid.vcf --]
[-- Type: text/x-vcard, Size: 385 bytes --]

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


  reply	other threads:[~2006-11-08  0:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 11:52 gitk feature request Pierre Marc Dumuid
2006-11-07 22:12 ` Paul Mackerras
2006-11-07 22:34   ` Junio C Hamano
2006-11-08  0:06     ` Pierre Dumuid [this message]
2006-11-11 15:08     ` Marco Costalba
2006-11-11 15:20       ` Jakub Narebski
2006-11-11 17:42     ` Petr Baudis
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 17:29 H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45511F8C.1060705@adelaide.edu.au \
    --to=pierre.dumuid@adelaide.edu.au \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.