From b1704f4e12b09628f625b244be5d353a165e51de Mon Sep 17 00:00:00 2001 From: "kartynnik@c8b57e8688e66fe58144cae5833b23948ae9b599" Date: Mon, 29 Aug 2016 17:30:45 +0000 Subject: Added a comment: Branch names containing slashes --- doc/sync/comment_20_537b27219871a565ae7bb7f357cd3793._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/sync/comment_20_537b27219871a565ae7bb7f357cd3793._comment (limited to 'doc') diff --git a/doc/sync/comment_20_537b27219871a565ae7bb7f357cd3793._comment b/doc/sync/comment_20_537b27219871a565ae7bb7f357cd3793._comment new file mode 100644 index 000000000..4a3721eb6 --- /dev/null +++ b/doc/sync/comment_20_537b27219871a565ae7bb7f357cd3793._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="kartynnik@c8b57e8688e66fe58144cae5833b23948ae9b599" + nickname="kartynnik" + subject="Branch names containing slashes" + date="2016-08-29T17:30:44Z" + content=""" +1) When I have a branch \"some/branch/name\" containing slashes in its name, git-annex sync strips everything up to the last slash and creates \"synced/name\", which may clash with \"some/other/name\". Is there a workaround? + +2) Could the \"don't use synced branches\" behavior referred in the comments above somehow be configured on the repository side so that everyone cloning it doesn't need to configure it for himself? +"""]] -- cgit v1.2.3