Hi Ludo, Ludovic Courtès <[email protected]> writes:
> It supports unrelated Git histories. It could really be called > ‘--allow-anything’ but I thought it’d be less descriptive. :-) > > If you hit a problem with that, please report it (perhaps I just > overlooked it in the other issue.) Oh nice, then this whole issue I think should be to report that --allow-downgrades does not allow everything. When I first reported the issue I tried --allow-downgrades thanks to some help on IRC. The first attempt failed as I mentioned previously in the thread. However I did just try --allow-downgrades again after a rebase and it seems to have succeeded. With that, I think this issue can be closed. Thanks for thinking of this case! > Interesting, I hadn’t thought about how this mechanism would give an > incentive to have a channel vs. contributing directly upstream. I think I will add some notes about a rebase workflow and --allow-downgrades to the contributing documentation. Looking just now I'm not sure using a local source tree as a channel is mentioned in the documentation either. I will open a different patch set to deal with those issues. > Normally, ‘--allow-downgrades’ does exactly what you need, at least > that’s the intent. I’d argue that it’s also reasonable to use it in > this case because obviously you know what you’re doing, and you’re > pulling from a local Git repository, so that’s fine. 100% it does what I need. Thanks again, feel free to close. - John
