On 19/09/19 12:11PM, Denton Liu wrote: > On Fri, Sep 20, 2019 at 12:33:59AM +0530, Pratyush Yadav wrote: > > On 19/09/19 11:47AM, Denton Liu wrote: > > > For the record, you could do a > > > > > > git cherry-pick -Xsubtree=git-gui 00ddc9d13c 7560f547e6 > > > > > > to bring them over instead of manually recreating the changes yourself. > > > Personally, I'd prefer the cherry-picked commits as it'd preserve > > > authorship information but I'm not sure how Junio feels. > > > > I'm not sure how this will work internally, but won't this also pull all > > the ancestors of those commits into git-gui? That is bloat I'd rather > > avoid. > > > > I tried creating branches for those two commits and then did a subtree > > Since those two commits have parents that are found in git.git, you'll > pull the whole history of git.git if you try doing this. > > > pull, and that is what happened. The repo size went up from around 6M to > > 72M. Will cherry-picking avoid that? > > > > Yes, when you cherry-pick, you're essentially replaying the patch from > the old tree onto the new tree and recording a fresh commit from it. The > new commit is completely separate from the one it's based on so you > won't end up pulling in any ancestry information and, as a result, you > won't pull the rest of git's history. > > In any case, give it a try. It doesn't hurt to experiment and play > around with it. It works. Thanks. -- Regards, Pratyush Yadav
