git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Arnott" <andrewarnott@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Samuel Tardieu" <sam@rfc1149.net>, git@vger.kernel.org
Subject: Re: How to rewrite author history
Date: Sat, 22 Mar 2008 12:06:37 -0700	[thread overview]
Message-ID: <216e54900803221206l39d61bcw1c546b9812968ac0@mail.gmail.com> (raw)
In-Reply-To: <20080322165737.GB7611@coredump.intra.peff.net>

Thanks, Jeff.  That was very helpful.  I have published my repo online
already, but only a couple people (if even that) have cloned it by now
and I am prepared to email the list of interested parties letting them
know.  About this rebasing thing, is there a better way than for them
to just wipe their repo and clone again?  Would a simple git fetch and
git rebase do the trick?

Thanks again, everyone.

On Sat, Mar 22, 2008 at 9:57 AM, Jeff King <peff@peff.net> wrote:
> On Sat, Mar 22, 2008 at 06:11:12AM -0700, Andrew Arnott wrote:
>
>  > git-filter-branch --env-filter '
>  > [...]
>
> > And I did this for master, and my v1 and v0.1 branches.  I'm concerned
>  > though, that since I changed the names of all the objects by doing
>  > this, did I somehow make my branches incompatible with each other?
>  > Will there be any problems in the future sharing commits or merging
>  > across branches as a result?
>
>  There are two concerns, and I'm not sure which you have (I think number
>  1):
>
>   1. Your branches within the repository will not connect anymore. I
>      believe this is a non-issue with your filter, since the generated
>      commit IDs are deterministic. Certainly a toy case worked for me
>      with:
>
>        for i in master branch; do
>          git filter-branch --env-filter=... $i
>        done
>
>      You can also specify both to be done at the same time, which is
>      more efficient:
>
>        git filter-branch --env-filter=... master branch
>
>      You can check the graph structure with "gitk master branch" which
>      should show them connecting.
>
>   2. Your branches are now a different, rewritten history compared to
>      anyone who has cloned or fetched from you. This is unavoidable, and
>      the answer is either "don't use filter-branch" or "tell everyone to
>      rebase their work on the new history." So the best time to
>      filter-branch is right after import, but before you start work.
>
>  -Peff
>



-- 
Andrew Arnott

  reply	other threads:[~2008-03-22 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <216e54900803210938q4981b5d1t535af419f5b15ad8@mail.gmail.com>
2008-03-21 16:41 ` How to rewrite author history Andrew Arnott
2008-03-21 18:40   ` Dmitry Potapov
2008-03-22  9:29   ` Samuel Tardieu
2008-03-22 13:11     ` Andrew Arnott
2008-03-22 16:57       ` Jeff King
2008-03-22 19:06         ` Andrew Arnott [this message]
2008-03-23  7:09           ` Jeff King

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=216e54900803221206l39d61bcw1c546b9812968ac0@mail.gmail.com \
    --to=andrewarnott@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sam@rfc1149.net \
    /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).