threads / discuss / 39930

git history in a file

Subject: git history in a file

## tl;dr

3 messages between Jul 24, 2015 and Jul 24, 2015.

replies: 2people: 2as markdown or json

Josh Boyer· Jul 24, 2015, 12:16 UTC · lore

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

Andreas Schwab· Jul 24, 2015, 12:46 UTC · re: Josh Boyer · lore

Re: git history in a file

Josh Boyer <jwboyer@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, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Josh Boyer· Jul 24, 2015, 13:02 UTC · re: Andreas Schwab · lore

Re: git history in a file

On Fri, Jul 24, 2015 at 8:46 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:

Show 8 quoted lines

> Josh Boyer <jwboyer@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