Git submodules are pointers to other git commits. Therefore, any component changes made don’t affect the mono repo until you update said mono repo to point to the new commit. If you do this to point at the latest release tags, this makes for less updates. Otherwise, you’ll want to figure out a CI system for automatically updating submodules to the latest master commits as they pass CI.
On Mon, Aug 31, 2020 at 05:17 sebb <seb...@gmail.com> wrote: > On Sun, 30 Aug 2020 at 15:01, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins <chtom...@gmail.com> wrote: > > > > > > > > > > > > > > > > On Aug 30, 2020, at 9:44 AM, sebb <seb...@gmail.com> wrote: > > > > > > > > > > Some questions: > > > > > > > > > > - does it affect any existing usage? > > > > > i.e. can people continue to use the individual repos exactly as > before > > > > > > > > no they can’t > > > > > > > > > > Yes they can... this would be a new repo, and changes nothing for current > > > usage. This does not affect existing repos. > > > > What about my other queries? > > > > - changes to commit messages: > > can people commit to components directly from the new repo? > > If so, does that change the commit messages? > > > > - maintenance of the new repo: > > what is involved, and how will the project know when updates are needed? > > > > > Gary > > > > > > > > > > > > > > > > > - does it affect Git emails in any way? > > > > > e.g. do they have different text? > > > > > > > > same emails > > > > > > > > > > > > > > - will it need much maintenance? > > > > > If so, how do we know when it needs updating? > > > > > > > > more maintainance, have to maintain a git hash at a symlink pointing > to an > > > > external repository > > > > > > > > -Rob > > > > > > > > > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory <garydgreg...@gmail.com> > > > > wrote: > > > > >> > > > > >> Yes yes "girl" -> "git" > > > > >> > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory <garydgreg...@gmail.com> > > > > wrote: > > > > >> > > > > >>> I'm talking about girl's own submodules: > > > > >>> > > > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules > > > > >>> > > > > >>> https://git-scm.com/docs/git-submodule > > > > >>> > > > > >>> Gary > > > > >>> > > > > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins <chtom...@gmail.com> > wrote: > > > > >>> > > > > >>>> By git submodules, are you talking about a symlink to another git > > > > >>>> repository inside one of our repositories? > > > > >>>> > > > > >>>> -Rob > > > > >>>> > > > > >>>>> On Aug 29, 2020, at 6:52 PM, Gary Gregory < > garydgreg...@gmail.com> > > > > >>>> wrote: > > > > >>>>> > > > > >>>>> Hi All, > > > > >>>>> > > > > >>>>> Any thoughts for or against creating a new git repository which > would > > > > >>>>> contain all 'proper' Commons components as git submodules? > > > > >>>>> > > > > >>>>> The idea is to be able to checkout all of Commons 'proper' in > one go > > > > in > > > > >>>> one > > > > >>>>> place. > > > > >>>>> > > > > >>>>> Gary > > > > >>>> > > > > >>>> > > > > >>>> > --------------------------------------------------------------------- > > > > >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > >>>> For additional commands, e-mail: dev-h...@commons.apache.org > > > > >>>> > > > > >>>> > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > -- Matt Sicker <boa...@gmail.com>
