On Wed, Apr 10, 2024 at 11:10 PM Matthias Koeppe <matthiaskoe...@gmail.com> wrote:
> On Wednesday, April 10, 2024 at 2:40:18 PM UTC-7 Dima Pasechnik wrote: > > On Wed, Apr 10, 2024 at 9:02 PM Matthias Koeppe <matthia...@gmail.com> > wrote: > > On Wednesday, April 10, 2024 at 1:00:06 PM UTC-7 Dima Pasechnik wrote: > > On 10 April 2024 19:24:12 CEST, Matthias Koeppe <matthia...@gmail.com> > wrote: > >On Tuesday, April 9, 2024 at 3:28:27 PM UTC-7 Dima Pasechnik wrote: > >[...] git submodules [...] > > > >git submodules are included in a repository by specific commit sha of the > >submodule repo. > >So whenever one has to make a change in the submodule repo, one also has > to > >commit a change (by a second PR) in the main repo. > Why a 2nd PR? > > > I just explained it. To update the version (commit sha) of the submodule. > > > Have you ever worked with submodules? > > > Yes, Dima, I have. > > > There is simply no need to keep the .gitsubmodules - > the only file in the main repo affected by "git submodule update --remote" > - > always synchronized, commit-wise, for everyone. > > > There is. Without doing that, the changes made in the submodule won't take > effect. > This is not true. git submodule update --remote will pick up submodules changes just fine. Read the docs? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1niXYTBjvEgncLBxq9KyZEWdVBmSXRn6ab56OiX8s2AA%40mail.gmail.com.
