* [GSoC] [RFC] stashing unmerged index entries
@ 2019-04-09 8:16 Kapil Jain
2019-04-09 11:01 ` Duy Nguyen
0 siblings, 1 reply; 2+ messages in thread
From: Kapil Jain @ 2019-04-09 8:16 UTC (permalink / raw)
To: Thomas Gummerer, Johannes Schindelin, Duy Nguyen, me, git
Reference: https://git.github.io/SoC-2019-Ideas/#teach-git-stash-to-handle-unmerged-index-entries
"When the index is unmerged, git stash refuses to do anything. That is
unnecessary, though, as it could easily craft e.g. an octopus merge of
the various stages. A subsequent git stash apply can detect that
octopus and re-generate the unmerged index."
according to it we take the unmerged entries (caused by conflicted
merge) in index from all stages, and do an octopus merge. how does
this solve the problem, i mean where do those entries go after octopus
merge ? a conflicted merge is still there, do we store the merge
separately ?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [GSoC] [RFC] stashing unmerged index entries
2019-04-09 8:16 [GSoC] [RFC] stashing unmerged index entries Kapil Jain
@ 2019-04-09 11:01 ` Duy Nguyen
0 siblings, 0 replies; 2+ messages in thread
From: Duy Nguyen @ 2019-04-09 11:01 UTC (permalink / raw)
To: Kapil Jain; +Cc: Thomas Gummerer, Johannes Schindelin, Taylor Blau, git
On Tue, Apr 9, 2019 at 3:16 PM Kapil Jain <jkapil.cs@gmail.com> wrote:
>
> Reference: https://git.github.io/SoC-2019-Ideas/#teach-git-stash-to-handle-unmerged-index-entries
>
> "When the index is unmerged, git stash refuses to do anything. That is
> unnecessary, though, as it could easily craft e.g. an octopus merge of
> the various stages. A subsequent git stash apply can detect that
> octopus and re-generate the unmerged index."
>
> according to it we take the unmerged entries (caused by conflicted
> merge) in index from all stages, and do an octopus merge. how does
> this solve the problem, i mean where do those entries go after octopus
> merge ?
I'm not even into git-stash, but it does sound like it solves the
problem, which is _restoring_ the conflict after you unstash. Since
you have all the unmerged entries in the merge (which is stored in
some stash ref), you can safely destroy all conflicts in worktree and
put it back to a clean state. When people want to apply the stash, you
re-generate the unmerged index from the octopus merge.
> a conflicted merge is still there,
yes, but because you can restore it later now, you can remove the
conflict safely. That's what git-stash is for.
> do we store the merge separately ?
--
Duy
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-04-09 11:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-09 8:16 [GSoC] [RFC] stashing unmerged index entries Kapil Jain
2019-04-09 11:01 ` Duy Nguyen
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).