From: Paul Gardiner <osronline@glidos•net>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: git@vger•kernel.org, osronline@glidos•net
Subject: Re: All I wanted was git-fast-export
Date: Sun, 17 Feb 2008 17:00:08 +0000 [thread overview]
Message-ID: <47B86818.7010706@glidos.net> (raw)
In-Reply-To: <alpine.LSU.1.00.0802101248260.11591@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> [please do not look the other way when you respond to me, i.e. do not cull
> me from the Cc: list. Thankyouverymuch]
>
> On Sun, 10 Feb 2008, Paul Gardiner wrote:
>
>> Johannes Schindelin wrote:
>>
>>> The thing is, filter-branch was _written for this purpose_. So if you
>>> know what commit you rewrote last, you can make the process
>>> faster/safer by issuing
>>>
>>> $ git filter-branch --msg-filter="<blabla>" <old-commit>..master
>> That does look just what I need, but did you see the reason I thought I
>> couldn't use it? I need to repeatedly sync the git repository from a
>> live cvs repository, and repeatedly filter the new commit messages.
>
> Oh, I thought you saw why I put in that "<old-commit>...". You do not
> really need it, as filter-branch will come up with the _same_ commit
> hashes, unless _something_ was changed.
>
> IOW if you have only commits without that "Summary: " prefix, the
> filter-branch call will be a (not so cheap) no-op.
>
> But of course, I meant to suggest (admittedly, in a very short short-hand)
> that you use "git filter-branch ... origin@{1}..origin" after cvsimport.
I'm still struggling a bit to understand ref specs. I'm using --all at
the moment, but that's very slow. What I need is to filter the new
commits of all branches. Will origin@{1}..origin do that, or does
it just affect master?
P.
prev parent reply other threads:[~2008-02-17 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 17:27 All I wanted was git-fast-export Paul Gardiner
2008-02-09 18:04 ` Johannes Schindelin
2008-02-09 22:44 ` Paul Gardiner
2008-02-10 0:58 ` Johannes Schindelin
2008-02-10 10:07 ` Paul Gardiner
2008-02-10 12:51 ` Johannes Schindelin
2008-02-10 15:39 ` Paul Gardiner
2008-02-13 9:10 ` Paul Gardiner
2008-02-17 17:00 ` Paul Gardiner [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=47B86818.7010706@glidos.net \
--to=osronline@glidos$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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