If you did do the rename, the next time someone did a `git fetch`, git would warn that there was no matching history. If they subsequently do a `git merge origin/master` (or if they just ran `git pull` in the first place), there probably won't be any conflicts (especially if the files are all the same), however their local history would not match the remote history - they would have a local merge commit whose parents were the new 'origin/master' and the old 'origin/master'. If anyone with push rights tried to push this (and succeeded), all the old history would be reintroduced again.
A way to avoid this is to run `git pull --rebase` or `git fetch && git rebase origin/master` once after the rename, but it's often difficult to educate users of git to do this. However, looking at the number of committers, this might not be too difficult. You could also watch for all the pushes at code review time, and ensure no one is pushing the old history. It's up to the project owners to decide if this is worthwhile. On Thursday, 23 October 2014 11:00:56 UTC-4, Jakob Kummerow wrote: > > The reason for creating a new repository instead of replacing the old one > was that all commit hashes are changing [1]. We suspected it might cause > confusion for existing clones of github.com/v8/v8 if we replaced the > contents of that repo. If someone could say with certainty that this would > not be a problem, then sure, we could re-use the old repo name. > > [1] This is due to how git-svn works. Every git-svn checkout of an SVN > repository, including the existing github.com/v8/v8 mirror, has its own > unique hashes. After the move to git as the source of truth, > chromium.googlesource.com/v8/v8.git will be the authoritative source of > all commit hashes, and all clones/checkouts will share them, including the > new github mirror.) > > On Thu, Oct 23, 2014 at 2:16 PM, Mathias Bynens <math...@opera.com > <javascript:>> wrote: > >> On Thu, Oct 23, 2014 at 1:23 PM, Ben Noordhuis <in...@bnoordhuis.nl >> <javascript:>> wrote: >> > On Thu, Oct 23, 2014 at 12:56 PM, C. Ken <nvc...@gmail.com >> <javascript:>> wrote: >> >> what is actually mean of "WILL BE DEPRECATED SOON" say on v8 github >> repo >> >> https://github.com/v8/v8 >> > >> > Scroll down, it's on the page. :-) V8 is moving to git, that's why >> > the svn->git mirror is going away. Use [0] or [1] instead. >> > >> > [0] https://chromium.googlesource.com/v8/v8.git >> > [1] https://github.com/v8/v8-git-mirror >> >> GitHub supports renaming repositories, so once v8/v8 is deleted, >> v8/v8-git-mirror could be renamed to v8/v8. GitHub would then >> automatically set up redirects from v8/v8-git-mirror to v8/v8. >> >> -- >> -- >> v8-users mailing list >> v8-u...@googlegroups.com <javascript:> >> http://groups.google.com/group/v8-users >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to v8-users+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
