latest 20 messages by tgp_
+
[2016-08-25T05:53:32Z]
tgp_
another approach would be to add a new remote, `git remote add neworigin <new-url>` and then do `git push neworigin master` instead
+
[2016-08-25T05:52:52Z]
tgp_
a git remote repository has a name ("origin") and a url. if your repository was renamed on github, then the url changed, but you can still use the same name offline
+
[2016-08-25T05:51:11Z]
tgp_
the command I write changes the url of the `origin` repository in your local copy, so if that works out, then you can do git push origin master afterwards
+
[2016-08-25T05:48:52Z]
tgp_
you can just `git remote set-url origin <new-url>` and it should work
+
[2016-08-25T05:48:15Z]
tgp_
haha :D
+
[2016-08-25T05:47:58Z]
tgp_
worked out?
+
[2016-08-25T05:37:28Z]
tgp_
that looks good. now you can push
+
[2016-08-25T05:33:55Z]
tgp_
and if that output looks ok, you should push
+
[2016-08-25T05:33:40Z]
tgp_
git rm, then commit, then bfg, then show me again the log of that
+
[2016-08-25T05:33:28Z]
tgp_
are you joking? :-)
+
[2016-08-25T05:33:06Z]
tgp_
yes
+
[2016-08-25T05:32:48Z]
tgp_
and then post again the output of that bfg run
+
[2016-08-25T05:32:17Z]
tgp_
hmmmm, I guess you would have more success if you read what people here write. you need to commit after git rm, and *then* run bfg again
+
[2016-08-25T05:31:24Z]
tgp_
did you commit before?
+
[2016-08-25T05:31:20Z]
tgp_
if you git rm and commit, then it is gone from the current HEAD, but is still in the previous commit
+
[2016-08-25T05:30:15Z]
tgp_
you need to `git rm` it, commit, then run the bfg command again
+
[2016-08-25T05:30:04Z]
tgp_
the file is gone from the history, but it is still in the current commit.
+
[2016-08-25T05:29:54Z]
tgp_
not yet
+
[2016-08-25T05:29:47Z]
tgp_
ok. do you understand what the program is saying?
+
[2016-08-25T05:26:45Z]
tgp_
that's quick