Re: [VSS] Splitting tools into separate repository

On Thu, 2020-02-20 at 23:41 +0000, Magnus Feuer wrote:
> Gunnar,
> 
> I am starting to work through the build system.
> 
> Do you want me to create a branch inside your private vss-tools and
> vehicle_signal_specification forks and submit PRs from my branches to
> your master?

Sure, if you need to get started, you can do this now on the fork.
I will move the repo to the GENIVI account at the earliest tomorrow.

- Gunnar


> 
> 
> /Magnus F.
> -------------------
> System Architect Manager
> Jaguar Land Rover
> 
> Email: mfeuer1@jaguarlandrover.com 
> Mobile: +1 949 294 7871
> 
> 
> 
> Jaguar Land Rover North America, LLC
> 1450 NW 18th Ave, Portland, OR 97209
> -------------------
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF 
> Registered in England No: 1672070
> 
> This e-mail and any attachments contain confidential information for
> a specific individual and purpose.  The information is private and
> privileged and intended solely for the use of the individual to whom
> it is addressed.  If you are not the intended recipient, please e-
> mail us immediately.  We apologise for any inconvenience caused but
> you are hereby notified that any disclosure, copying or distribution
> or the taking of any action in reliance on the information contained
> herein is strictly prohibited.
> 
> This e-mail does not constitute an order for goods or services unless
> accompanied by an official purchase order.
> 
> 
> From: Gunnar Andersson <gandersson@genivi.org>
> Sent: Wednesday, February 19, 2020 03:56
> To: Magnus Feuer <mfeuer1@jaguarlandrover.com>; 
> Daniel.DW.Wilms@bmw.de <Daniel.DW.Wilms@bmw.de>
> Cc: public-automotive@w3.org <public-automotive@w3.org>
> Subject: [VSS] Splitting tools into separate repository
>  
> Magnus, Daniel, and all:
> 
> As you requested on yesterday's W3C Automotive WG call I have done
> the steps to splitting of tools from the signal repository in VSS.
> 
> I show the example of a separate repository named vss-tools:
> For now it is kept on a fork [1]
> 
> As expected git-subtree seems to have stored the relevant history
> from
> the original repository (only those commits that pertain to changes
> inside the tools directory) in the history of vss-tools repository.
> 
> I added an empty commmit with some information to document
> the point at which we did the split, for the future. [2]
> 
> Finally, I replaced the original tools directory from the VSS
> repo with a submodule reference to vss-tools. [3]
> 
> NOTE that that commit renames tools/ to vss-tools/!
> ! All users should give your viewpoint on that, how much it affects
> things like build environments, etc.  I think keeping directory names
> the same as the submodule is usually the best, but it involves a path
> change here.  Thoughts?
> 
> If everything looks good we can repeat the same operations
> under the GENIVI account.  I would also propose you, Magnus, also
> sign
> off on commits [2] and [3].  I can add this when I do the final
> cleanup
> if you say OK.
> 
> @ Daniel There was one small oddity and that is that it seems 
> tools had a submodule already, which I was not aware of, located at
> tools/documentation/themes/learn.  This one did not carry over to the
> new vss-tools repo (Please see [3] for details) but it feels somewhat
> unrelated to our project.  If it is used only as documentation for 
> maintenance of the wiki, maybe keeping a link to the project would be
> enough?
> 
> Sincerely,
> - Gunnar
> 
> [1] https://github.com/gunnarx/vss-tools

> [2] 
> https://github.com/gunnarx/vss-tools/commit/2993ed430f7f36af12496e3e6c3ba546153ba106

> [3] 
> https://github.com/gunnarx/vehicle_signal_specification/commit/c1f486a7a733947ff658d0535d634e03008aa63b

>

Received on Friday, 21 February 2020 00:18:51 UTC