git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Enrico Weigelt <weigelt@metux.de>
Cc: git@vger.kernel.org
Subject: Re: Using a different index and HEAD
Date: Sat, 13 Nov 2010 09:25:46 -0800 (PST)	[thread overview]
Message-ID: <m3aaldf863.fsf@localhost.localdomain> (raw)
In-Reply-To: <20101113152906.GA24903@nibiru.local>

Enrico Weigelt <weigelt@metux.de> writes:

> I'm currently thinking about an IDE toolkit entirely based on git,
> which eg. versions every single file save operation (so, IOW: an
> separately versioned workdir) automatically and later allows to
> rebase/rework this to tell what really gets committed to the
> actual working branch. For this multiple indices and refs/HEAD
> pointers would be very helpful.

UGFWIWNI (Using Git For What It Was Not Intended) ;-) ?

> 
> Is there already a way to tell other locations for index file
> and current HEAD symref on command line (just like we have w/
> --work-dir etc) ?

There is GIT_INDEX_FILE environment variable (see git(1) manpage);
you can maniplate symrefs such as HEAD directly using git-symbolic-ref
(and git-show-ref, git-rev-parse, etc.).

You can also check 'contrib/workdir/git-new-workdir' script.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2010-11-13 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 15:29 Using a different index and HEAD Enrico Weigelt
2010-11-13 17:25 ` Jakub Narebski [this message]
2010-11-21 15:16   ` Tomas Carnecky
     [not found] ` <20101113160546.GA5535@burratino>
2010-11-13 19:41   ` Enrico Weigelt
2010-11-13 20:21     ` Jonathan Nieder

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=m3aaldf863.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=weigelt@metux.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).