On Mon, 4 Mar 2013 08:01:40 -0800 (PST)
banaca...@gmail.com wrote:

> I have a clone of a local repo that has so many significant updates
> that it really needs to be a major release.  I'm thinking that it
> should be new repo, so I want to disconnect it from the old repo.
> What is the best way to handle this?  Should I (can I) delete the
> origin/HEAD origin/master? What about the clone pointer in the
> original repo?

$ git remote remove origin

Should make your repository has no traces of what was your "origin"
remote.  You could also just rename "origin" to something else and add
another remote named "origin" in its place -- the name "origin" is
really nothing special, it's just the name `git clone` uses by default.

What I do not get though is why you think it's a good idea to create a
disconnected repo for a new release.  This is not Mercurial with its
"one directory per checkout" paradigm.  No matter how many commits you
did in your clone, you can push them all to the "origin" with little to
no effort.  So could you please provide more background for your use

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to