Re: [boost] [git] Near future.. How do we deal with git-native libraries?
-----Mensaje original----- De: Boost [mailto:boost-bounces@lists.boost.org] En nombre de Daniel James Enviado el: jueves, 05 de diciembre de 2013 0:57 Para: boost@lists.boost.org Asunto: Re: [boost] [git] Near future.. How do we deal with git-native libraries? On 4 December 2013 21:49, Joaquin M Lopez Munoz <joaquin@tid.es> wrote:
Being both the author of Boost.MultiIndex and a total Git neophyte, could you please explain to me how this lack of ref commits affect me and whether I can fix it myself?
It means that when someone checks out the master project they don't get the latest versions of the submodules. I'm just updating the master project now.
I understand this is https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96... Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project. Thank you, Joaquín M López Muñoz Telefónica Digital ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx
On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
I understand this is
https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...
Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project.
Currently it needs to be done manually. Eventually it should be scripted, hopefully from a git hook so that it's pretty fast. There's some dispute about how the changes should be propagated to the main module.
Daniel James <daniel@calamity.org.uk> writes:
On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
I understand this is
https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...
Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project.
Currently it needs to be done manually. Eventually it should be scripted, hopefully from a git hook so that it's pretty fast. There's some dispute about how the changes should be propagated to the main module.
IMO boostorg/boost's master branch shouldn't get updated to a state X until X passes regression testing. -Dave
On 7 December 2013 22:54, Dave Abrahams <dave@boostpro.com> wrote:
Daniel James <daniel@calamity.org.uk> writes:
On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
I understand this is
https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...
Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project.
Currently it needs to be done manually. Eventually it should be scripted, hopefully from a git hook so that it's pretty fast. There's some dispute about how the changes should be propagated to the main module.
IMO boostorg/boost's master branch shouldn't get updated to a state X until X passes regression testing.
Is this something you're willing to automate? I don't think anyone will want to do that manually.
Daniel James <daniel@calamity.org.uk> writes:
On 7 December 2013 22:54, Dave Abrahams <dave@boostpro.com> wrote:
Daniel James <daniel@calamity.org.uk> writes:
On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
I understand this is
https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...
Excuse my ignorance but: does this mean syncing between the master project and submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project.
Currently it needs to be done manually. Eventually it should be scripted, hopefully from a git hook so that it's pretty fast. There's some dispute about how the changes should be propagated to the main module.
IMO boostorg/boost's master branch shouldn't get updated to a state X until X passes regression testing.
Is this something you're willing to automate? I don't think anyone will want to do that manually.
It's easy enough to do manually, IMO. It would certainly be better to have it automated. I don't have time to work on Boost for the forseeable future, so no, I won't be automating it.
On Sat, Dec 7, 2013 at 5:54 PM, Dave Abrahams <dave@boostpro.com> wrote:
Daniel James <daniel@calamity.org.uk> writes:
On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
I understand this is
https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...
Excuse my ignorance but: does this mean syncing between the master
project and
submodules need be done manually? I was assuming that somehow updates to a submodule automatically propagate to checkouts of the master project.
Currently it needs to be done manually. Eventually it should be scripted, hopefully from a git hook so that it's pretty fast. There's some dispute about how the changes should be propagated to the main module.
IMO boostorg/boost's master branch shouldn't get updated to a state X until X passes regression testing.
+1 We aren't there yet, although the conversion to git and modular boost has put us a lot closer than we were. Daniel is, IIUC, trying to address the question of what we do right now. --Beman
participants (4)
-
Beman Dawes -
Daniel James -
Dave Abrahams -
JOAQUIN M. LOPEZ MUÑOZ