git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Enrico Weigelt <weigelt@metux.de>, Jakub Narebski <jnareb@gmail.com>
Subject: Re: Using a different index and HEAD
Date: Sat, 13 Nov 2010 14:21:46 -0600	[thread overview]
Message-ID: <20101113202146.GA16920@burratino> (raw)
In-Reply-To: <20101113194128.GA8878@nibiru.local>

Enrico Weigelt wrote:

> I didnt have time for a deeper look yet, but I'll try to explain
> my ideas a bit more:
>
> Suppose I choose to work on an branch "one" (which probably is
> synced to some remote). That will create some temporary (local)
> WIP branch, where
[...]
>              Now I click some "commit" button and it asks me what
> exactly to commit - I now can interactively selected changes to
> be committed (maybe even on single changelets within a file),
> they'll be squashed together (maybe involving some rebase magic)
> and an commit final commit object is created on the "one" branch.

Ah, that is completely different. :)  Your tools would be

	GIT_INDEX_FILE=$GIT_DIR/wip-index; export GIT_INDEX_FILE
	git update-index ...
	git write-tree
	git commit-tree ...
	git update-ref ...
	git read-tree ...

none of which touch HEAD except the second to last one.

See the list of "low-level commands (plumbing)" and examples in
contrib/examples for more details.

      reply	other threads:[~2010-11-13 20:22 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
     [not found] ` <20101113160546.GA5535@burratino>
2010-11-13 19:41   ` Enrico Weigelt
2010-11-13 20:21     ` Jonathan Nieder [this message]

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=20101113202146.GA16920@burratino \
    --to=jrnieder@gmail.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).