There was a tutorial'ish post here on the list a few days ago about named
remotes. If you clone a remote repository, a named remote is created,
called "origin", and your local master (or whatever) branch is set to track
Now if you change origin's URL (git remote --set-url user@host:new-repo.git),
and do a git push, your changes will go to the new repo.
On 28 Aug 2013 16:55, "Jaace" <jb5...@gmail.com> wrote:
> Here's my situation and I need advice on what the best way to handle it is
> as I'm newer to Git. I'm using these repositories as my own and I'm not
> working in tandem with anyone else but I want to keep my workflow clean and
> able to incorporate anybody I add to the project later. Here goes:
> I made a repo as a starting point for all my projects -- the idea here is
> to clone this repo to use as a base for any new project I start. I want to
> be able to clone it and then never check it back into the repo I cloned it
> from, but instead create a *new* repo for that specific project.
> When you clone a repo, it sets up a .git directory and all that but if I
> were to push any changes, that would push them back to the original I
> cloned it from, right? So is the proper way to go about doing what I want
> to simply delete the .git directory that comes with the cloned copy and
> just git init a new one or is there a better way to do this?
> 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.
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
For more options, visit https://groups.google.com/groups/opt_out.