From: Andreas Schwab <schwab@linux-m68k.org>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git history in a file
Date: Fri, 24 Jul 2015 14:46:49 +0200 [thread overview]
Message-ID: <87wpxp4tae.fsf@igel.home> (raw)
In-Reply-To: <CA+5PVA6S69ZU5Q432PK3DiPGkT=00tAtgSzJaYHyXLkHkg9FHw@mail.gmail.com> (Josh Boyer's message of "Fri, 24 Jul 2015 08:16:19 -0400")
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."
next prev parent reply other threads:[~2015-07-24 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 12:16 git history in a file Josh Boyer
2015-07-24 12:46 ` Andreas Schwab [this message]
2015-07-24 13:02 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpxp4tae.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=jwboyer@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.