git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Enrico Weigelt <weigelt@metux.de>, git@vger.kernel.org
Subject: Re: Using a different index and HEAD
Date: Sun, 21 Nov 2010 16:16:15 +0100	[thread overview]
Message-ID: <4CE937BF.9010606@dbservice.com> (raw)
In-Reply-To: <m3aaldf863.fsf@localhost.localdomain>

On 11/13/10 6:25 PM, Jakub Narebski wrote:
> 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) ;-) ?

I haven't seen anyone UGFWIINI for in a long time. Either that or my 
perception of 'not intended for' has changed. Maybe we should make a 
second round of the contest and see what use cases people came up with 
since the first UGFWIINI round (it's been almost two years). I'd 
certainly be interested :)

tom

  reply	other threads:[~2010-11-21 15:16 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
2010-11-21 15:16   ` Tomas Carnecky [this message]
     [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=4CE937BF.9010606@dbservice.com \
    --to=tom@dbservice.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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).