Skip to content

vendor.md: suggest doc clarification/caveat around rsync #64

Open
@cemeyer

Description

@cemeyer

Thanks for drafting these documents; in general, the vendoring process has been more straightforward than our previous SVN system.

One caveat I'd call out is the rsync -va --del ~/git/NetBSD/usr.sbin/mtree/ . at Update the Sources in the Vendor Branch.

The rsync --del will nuke the worktree's .git file in the vendor worktree. To work around this, save a copy of the .git file in the parent directory before rsync and restore it afterwards. This is ugly, but if you tell rsync to ignore .git instead, it will delete the file as not-present in the source directory. Maybe someone more familiar with rsync has an incantation to avoid clobbering worktrees.

(As a personal preference: the rsync -v (verbose) flag is just spam for any vendor software with a significant number of files. git status will tell you what changed, and that's more important. My 2¢.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions