use git-submodule for libraries #1

Open

laforge wants to merge 3 commits from laforge/submodule into master

laforge commented

2022-05-01 11:49:37 +00:00

Owner

Instead of copying all the library code, import it as a submodule from the new osmocom-analog-libraries.git

laforge added 3 commits 2022-05-01 11:49:37 +00:00

6a2a3dca26 re-structure directory tree in preparation of submodules

This moves src/lib* to src/lib/lib* so that we can replace it
with the osmocom-analog-libraries.git submodule in a subsequent
commit.

870fc7e976 remove src/lib from this repository, prepare for submodule

The contents of src/lib will be replaced with a submodule
in a following commit.

0dacb3a38c introduce git submodule for src/lib

This means that clones now have to use 'git clone --recursive'
or existing clones have to manually do 'git submodule init && git
submodule update'.

The advantage is that the new library submodule can be used from other
projects like osmo-cc-* without code duplication.

laforge requested review from jolly 2022-05-01 12:25:10 +00:00

This pull request has changes conflicting with the target branch.

configure.ac
src/Makefile.am
src/isdn/Makefile.am
src/isdn/dss1.c
src/isdn/ie.c
src/isdn/isdn.c
src/isdn/isdn.h
src/isdn/main.c
src/libjitter/jitter.c
src/libjitter/jitter.h

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b laforge/submodule master

git pull origin laforge/submodule

Step 2:

Merge the changes and update on Gitea.

git checkout master

git merge --no-ff laforge/submodule

git push origin master

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cc/osmo-cc-misdn-endpoint#1

No description provided.