Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Merge requests
  • !866

Consistent spelling of neighboring to fix #865

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge NeighboringConsistency into development Apr 25, 2016
  • Overview 14
  • Commits 7
  • Pipelines 0
  • Changes 33

Created by: SecUpwN

Thank you for submitting a pull request! Please add below details so that we can merge it faster.


Agreements

Please check these boxes to ensure you've actually read and understood these important rules!

  • I have reviewed and accepted the guidelines for contributing to this project.
  • I have reviewed and closely followed the Style Guide for this Android app.

Overview

Please add a short and easy to understand description of your proposed changes here.

This pull request shall fix the inconsistent spelling of neighboring in code and documentation.


Classification

Please click the correct checkbox that applies best to classify your pull request.

  • Bugfix (non-breaking change which fixes an existing issue)
  • New feature (non-breaking change which adds functionality)
  • Refactor (restructuring of existing code without changing its external functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

References

If your pull request is related to or solves any existing Issues, please link them here. #865 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: NeighboringConsistency