Ed Page

> --release vs. debug will result in different artifacts, > Another issue that might be harder to solve is the use of --target for cross-compilation, which can also change the...

I'm also interested in interactive rebase for `git-stack` (see my [issue](https://github.com/epage/git-stack/issues/41)). I wonder if our requirements align enough to allow a common edit format. The more we can standardize it,...

So a typical linear rebase would be > ``` > pick abc123 some root commit > pick abc456 first child > pick def456 first grandchild > ... > ``` That...

Another feature I've been considering (more important for `git-stack` than `git-branchless`) is modifying branch refs. This, combined with my parent commit idea, gets a little tricky in syntax - We...

I modeled `git stack`s core after `git rebase -i`, with two different levels (the higher level graph, the lower level list of instructions). In considering this, another model I thought...

Oh, from the summary, I missed that it was user-driven (since I only did a quick glance at the example). I'm assuming the use cases and users line up enough...

> Speaking in terms of mathematical relations, would you see the current bugreport functionality as a subset of the human-panic functionality? Or the other way around? I think I do...

@SirWindfield thats a great approach for helping with regressions; my concern when raising this issue is with ambiguities or misreadings of the spec. Having a common set of conformance tests...

Yes it is (sorry for the out of date link in the description). Thanks for the help! Whats interesting is it looks like we have some form of negative indexing...

Weird, I wonder why I originally thought this was about negative numbers. At least for the parts of liquid-rust I wrote, I wrote what I thought was the behavior. I...