From: Andreas Schwab <schwab@linux-m68k.org>
To: Henning Moll <newsScott@gmx.de>
Cc: git <git@vger.kernel.org>, Christian Couder <christian.couder@gmail.com>
Subject: Re: flatten-merge history
Date: Mon, 27 Oct 2014 19:45:38 +0100 [thread overview]
Message-ID: <874mupbbcd.fsf@igel.home> (raw)
In-Reply-To: <544D878D.6020809@gmx.de> (Henning Moll's message of "Mon, 27 Oct 2014 00:45:17 +0100")
Henning Moll <newsScott@gmx.de> writes:
> Just a final question: Is it possible to keep the GIT_COMMITTER_DATE in
> all those rebases?
If you want that you need to work with git filter-branch.
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."
prev parent reply other threads:[~2014-10-27 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 12:31 flatten-merge history Henning Moll
2014-10-26 5:46 ` Christian Couder
2014-10-26 14:36 ` Henning Moll
2014-10-26 15:19 ` Andreas Schwab
2014-10-26 19:02 ` Christian Couder
2014-10-26 23:45 ` Henning Moll
2014-10-27 18:45 ` Andreas Schwab [this message]
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=874mupbbcd.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=newsScott@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).