search for: unifiedrepo

Displaying 6 results from an estimated 6 matches for "unifiedrepo".

2016 Jul 29
4
[RFC] One or many git repositories?
...some point: Today: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/compiler_rt-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch - git svn dcommit - done Tomorrow with a monorepo: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/unifiedrepo-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch —directory=compiler-rt - git push - done Alternatively, if I’m upstream a patch once a year, I don’t really need to push it myself. - cd /path/to/compiler_rt-forked - git format-patch … - email the patch. > - Send...
2016 Jul 29
0
[RFC] One or many git repositories?
...> - git format-patch … > - cd /path/to/compiler_rt-upstream > - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch > - git svn dcommit > - done > > Tomorrow with a monorepo: > > - cd /path/to/compiler_rt-forked > - git format-patch … > - cd /path/to/unifiedrepo-upstream > - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch — > directory=compiler-rt > - git push > - done > > Alternatively, if I’m upstream a patch once a year, I don’t really need to > push it myself. > > - cd /path/to/compiler_rt-forked > - gi...
2016 Jul 29
2
[RFC] One or many git repositories?
.../path/to/compiler_rt-upstream >> - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch >> - git svn dcommit >> - done >> >> Tomorrow with a monorepo: >> >> - cd /path/to/compiler_rt-forked >> - git format-patch … >> - cd /path/to/unifiedrepo-upstream >> - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch — >> directory=compiler-rt >> - git push >> - done >> >> Alternatively, if I’m upstream a patch once a year, I don’t really need to >> push it myself. >> >> - cd /...
2016 Jul 29
0
[RFC] One or many git repositories?
...some point: Today: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/compiler_rt-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch - git svn dcommit - done Tomorrow with a monorepo: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/unifiedrepo-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch — directory=compiler-rt - git push - done Alternatively, if I’m upstream a patch once a year, I don’t really need to push it myself. - cd /path/to/compiler_rt-forked - git format-patch … - email the patch. - Send a pu...
2016 Jul 29
0
[RFC] One or many git repositories?
On 29 Jul 2016, at 05:11, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > What I meant by “different problem" is that “downstream users” for instance don’t need to commit, that makes their problem/workflow quite different from an upstream developer (for instance it is fairly easy to maintain a read-only view of the existing individual git repo currently on
2016 Jul 29
5
[RFC] One or many git repositories?
> On Jul 28, 2016, at 7:32 PM, Lang Hames <lhames at gmail.com> wrote: > > Hi Mehdi, > > This a narrow view IMO: the criteria #1 Chris mentioned to include projects in the monorepo was " must be tightly coupled to specific versions”. > It means that even with the test suite (and possibly some runtime) out of the monorepo, all the software that is tightly coupled