From: Sam Vilain <sam@vilain.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, Andreas Ericsson <ae@op5.se>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] contrib/fast-import: add perl version of simple example
Date: Tue, 18 Sep 2007 23:57:52 +1200 [thread overview]
Message-ID: <46EFBD40.1070102@vilain.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0709181217200.28586@racer.site>
Johannes Schindelin wrote:
>> I think he means a dump that you can meaningfully edit with sed or a
>> text editor. And even nicer, one that could be fed back into
>> git-fast-import. So you could do something like:
>>
>> git-fast-export A..B >dump
>> vi dump
>> git-fast-import <dump
>>
>> to rewrite history in a very flexible way.
>>
>
> Exactly what I meant. Some people seem to have problems with
> filter-branch, but somehow no proper bug report, let alone fix, evolved
> from that.
>
> I guess these people are more comfortable with what you just described.
>
Guilty. my own filter-branch supports things like custom re-ordering of
commits prior to rewriting (eg, if you need to refer to one commit to
another in a commit message, you better make sure it happens in the
right order).
I personally want to be able to dump patches, including merges, to
git-format-patch format, in such a way that all other information (eg,
committer, date, etc) is preserved. And probably using something akin to
Message-Id: headers for a "patch UUID" which is what you need when
you're working with piles of patches like that.
Sam.
next prev parent reply other threads:[~2007-09-18 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 7:26 [PATCH] contrib/fast-import: add perl version of simple example Jeff King
2007-09-18 7:27 ` Jeff King
2007-09-18 10:16 ` Johannes Schindelin
2007-09-18 10:28 ` Andreas Ericsson
2007-09-18 10:30 ` Jeff King
2007-09-18 11:18 ` Johannes Schindelin
2007-09-18 11:28 ` Andreas Ericsson
2007-09-18 11:57 ` Sam Vilain [this message]
2007-09-18 12:36 ` Johannes Schindelin
2007-09-18 13:25 ` Sam Vilain
2007-09-18 11:17 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46EFBD40.1070102@vilain.net \
--to=sam@vilain.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).