Displaying 5 results from an estimated 5 matches for "githubsubmod".
2016 Aug 04
3
Git move survey
Hi Tanya,
Do you have an idea on how we'll put up this survey online?
The other thread on the foundation list had some good proposals, but I
don't know how we'll make sure we follow all of them when we actually
publish it.
I'd like to have some process going before early Sep, so we can just
"put it up" as soon as all the proposals are finished.
Some questions...
Q1.
2016 Aug 17
2
Git move survey
...o unify it with the existing one (submodules…) along with the possible variants/options in a single document.
I plan to include examples of workflow today and after for each scenario, side-by-side. I hope to have it up for public review by the end of the month.
> http://llvm.org/docs/Proposals/GitHubSubMod.html <http://llvm.org/docs/Proposals/GitHubSubMod.html>
>
> I also don’t think this is a process that needs to be rushed. It will take awhile to publicize the survey and give people a chance to comment. Its more reasonable to give until Dec (1 month after the dev meeting BoF) give time...
2016 Jul 21
4
[RFC] One or many git repositories?
> -----Original Message-----
> From: mehdi.amini at apple.com [mailto:mehdi.amini at apple.com]
> Sent: Thursday, July 21, 2016 3:16 PM
> To: Robinson, Paul
> Cc: Renato Golin; Justin Lebar; llvm-dev at lists.llvm.org
> Subject: Re: [llvm-dev] [RFC] One or many git repositories?
>
>
> > On Jul 21, 2016, at 2:33 PM, Robinson, Paul via llvm-dev <llvm-
> dev at
2016 Jul 30
0
[RFC] One or many git repositories?
I talked with Majnemer/Mehdi about developing this proposal on github. They said that this was ok (after all we are moving to github). We can add facts to the specific proposal via PRs which we can use to center the discussion.
I created a straw man repo and a scaffolding hacked from the swift-evolution process for just this purpose. I hacked some words from jlebar's initial email as just a
2016 Jul 26
56
[RFC] One or many git repositories?
Hi Duncan,
> […]
> 2. Those working on projects *outside* the monolithic repo will get the downsides of both: a monolithic repo that they are only using parts of, and multiple repos that are somehow version-locked.
>
> 3. For many (most?) developers, changing to a monolithic git repo is a *bigger* workflow change than switching to separate git repos. Many people (and at least some