Re: clone breaks replace
- From
- Stephen Bash <bash@genarts.com>
- Date
- Jan 7, 2011, 21:15 UTC
- Message-ID
- <1351312.105443.1294434905621.JavaMail.root@mail.hq.genarts.com>
- In-Reply-To
- <20110107205103.GC4629@burratino>
----- Original Message -----
Show 12 quoted lines
> From: "Jonathan Nieder" <jrnieder@gmail.com> > To: "Phillip Susi" <psusi@cfl.rr.com> > Cc: git@vger.kernel.org, "Christian Couder" <chriscool@tuxfamily.org> > Sent: Friday, January 7, 2011 3:51:03 PM > Subject: Re: clone breaks replace > Phillip Susi wrote: > > > Isn't the whole purpose of using replace to avoid having to use > > filter-branch, which throws out all of the existing commit records, > > and creates an entirely new commit chain that is slightly modified? > > No. What documentation suggested that? Maybe it can be fixed.
I'll chime in here as another person who read the ProGit blog entry on git-replace [1] and came to the same conclusion Phillip (and I'm guessing others) did. OTOH when I attempted to read the actual git-replace manpage, I got completely lost, so I retained my (apparently incorrect) understanding from ProGit.
Thanks, Stephen
[1] http://progit.org/2010/03/17/replace.html