Re: git history in a file
Josh Boyer jwbo...@fedoraproject.org writes: I'm trying to figure out how to generate a file that contains the git history and changes from one revision to another, such that when the file is applied to a different tree starting at the same ancestor, the resulting tree is identical. See git-bundle(1). Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: git history in a file
On Fri, Jul 24, 2015 at 8:46 AM, Andreas Schwab sch...@linux-m68k.org wrote: Josh Boyer jwbo...@fedoraproject.org writes: I'm trying to figure out how to generate a file that contains the git history and changes from one revision to another, such that when the file is applied to a different tree starting at the same ancestor, the resulting tree is identical. See git-bundle(1). Thanks. That does indeed seem like what I'm looking for. josh -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
git history in a file
Hello, I'm trying to figure out how to generate a file that contains the git history and changes from one revision to another, such that when the file is applied to a different tree starting at the same ancestor, the resulting tree is identical. E.g. git whatever v4.2-rc3..master would produce this file, and then: git apply whatever file run on a tree which is currently at 4.2-rc3 would result in an identical HEAD. Originally I thought git-format-patch would be sufficient, however it does not contain merge commits and the resulting commit shas seem like they would be inaccurate. Is there a way to do this? I realize one could just git fetch/pull from tree A to tree B, but the usecase here is more complicated. Please CC me on replies as I am not subscribed. josh -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
