Re: bug?: stgit creates (unneccessary?) conflicts when pulling
- From
- Catalin Marinas <catalin.marinas@gmail.com>
- Date
- Feb 28, 2006, 18:53 UTC
- Message-ID
- <b0943d9e0602281053r675cee49i@mail.gmail.com>
- In-Reply-To
- <b0943d9e0602280700p132c6da2v@mail.gmail.com>
On 28/02/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
Show 13 quoted lines
> On 27/02/06, Catalin Marinas <catalin.marinas@gmail.com> wrote: > > An idea (untested, I don't even know whether it's feasible) would be to > > check which patches were merged by reverse-applying them starting with > > the last. In this situation, all the merged patches should just revert > > their changes. You only need to do a git-diff between the bottom and the > > top of the patch and git-apply the output (maybe without even modifying > > the tree). If this operation succeeds, the patch was integrated and you > > don't even need to push it. > > I tried some simple tests with the idea above. I attached a patch if > you'd like to try (I won't push it to the main StGIT repository yet. > For safety reasons, it only skips the merged patches when pushing > them. A future version could simply delete the merged patches.
Don't bother trying this patch. I just found a bug with git.reset() and the caching of the git.__head variable. I'll post another patch in a few hours.
-- Catalin