RFC: File format to allow us to track imported files

RFC: File format to allow us to track imported files

[Lars Kurth]

[-- Attachment #1.1: Type: text/plain, Size: 2194 bytes --]

Hi all,

following the recent discussion, we had on IRC and the action I had in the March
community call, I wanted to make a proposal related to the file format to track
files. I am not yet submitting a fully formed patch as there may be differing
opinions about the file format and name of the file.

I propose TRACKINGIMPORTS or for better readability TRACKING.IMPORTS in the
xen.git root as file name, but don’t have a strong opinion.

Ian originally proposed to add all information related to a mapping into
one single line. That however leads to VERY long lines. So, I decided to break
repository definitions into separate statements and allow referring to repos by
a shorthand.

That also has the advantage that should source repository locations ever change,
only a single line needs modification.

Let me know what you think.

Cheers
Lars

# This file contains information about source files that have been
# copied from other sources and need to be tracked
#
# The file may contain lines starting with ...
# --------------------------------------------
# version: of file format
# repo: repository definition
# manual|auto: a mapping to track files
#
# Repository Definitions are of the following format
# --------------------------------------------------
# repo name-of-source-repo git|svn https-url-of-source-repo
#
# Mappings to track files are of the following format
# ---------------------------------------------------
# manual|auto xen-file name-of-source-repo source-file commit-id
#
# auto: we can automatically update the file using a script
# manual: a committer needs to make a decision as to whether a
#   change is applied or ignored and update the last commit id
#   accordingly
# name-of-source-repo: must be defined by *repo*
# commit id: last commit id of source file that was deemed to be ok
#   and either imported into the tree or rejected
#
version 1

# Example of a repository definitions
repo linux-master git https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

# Example of a mapping
manual xen/drivers/passthrough/arm/smmu.c linux-master linux/drivers/iommu/arm-smmu.c b77cf11f094136

[-- Attachment #1.2: Type: text/html, Size: 8713 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] RFC: File format to allow us to track imported files

[Lars Kurth]

[-- Attachment #1.1: Type: text/plain, Size: 2194 bytes --]

Hi all,

following the recent discussion, we had on IRC and the action I had in the March
community call, I wanted to make a proposal related to the file format to track
files. I am not yet submitting a fully formed patch as there may be differing
opinions about the file format and name of the file.

I propose TRACKINGIMPORTS or for better readability TRACKING.IMPORTS in the
xen.git root as file name, but don’t have a strong opinion.

Ian originally proposed to add all information related to a mapping into
one single line. That however leads to VERY long lines. So, I decided to break
repository definitions into separate statements and allow referring to repos by
a shorthand.

That also has the advantage that should source repository locations ever change,
only a single line needs modification.

Let me know what you think.

Cheers
Lars

# This file contains information about source files that have been
# copied from other sources and need to be tracked
#
# The file may contain lines starting with ...
# --------------------------------------------
# version: of file format
# repo: repository definition
# manual|auto: a mapping to track files
#
# Repository Definitions are of the following format
# --------------------------------------------------
# repo name-of-source-repo git|svn https-url-of-source-repo
#
# Mappings to track files are of the following format
# ---------------------------------------------------
# manual|auto xen-file name-of-source-repo source-file commit-id
#
# auto: we can automatically update the file using a script
# manual: a committer needs to make a decision as to whether a
#   change is applied or ignored and update the last commit id
#   accordingly
# name-of-source-repo: must be defined by *repo*
# commit id: last commit id of source file that was deemed to be ok
#   and either imported into the tree or rejected
#
version 1

# Example of a repository definitions
repo linux-master git https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

# Example of a mapping
manual xen/drivers/passthrough/arm/smmu.c linux-master linux/drivers/iommu/arm-smmu.c b77cf11f094136

[-- Attachment #1.2: Type: text/html, Size: 8713 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel