From users-return-27784-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Tue Feb 5 11:27:06 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8C6CE180608 for ; Tue, 5 Feb 2019 12:27:05 +0100 (CET) Received: (qmail 52663 invoked by uid 500); 5 Feb 2019 11:27:04 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 52652 invoked by uid 99); 5 Feb 2019 11:27:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2019 11:27:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4A1801846D7 for ; Tue, 5 Feb 2019 11:27:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.798 X-Spam-Level: * X-Spam-Status: No, score=1.798 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6F4fGGxYc_pg for ; Tue, 5 Feb 2019 11:27:02 +0000 (UTC) Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com [209.85.128.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id C10DB60FB2 for ; Tue, 5 Feb 2019 11:27:01 +0000 (UTC) Received: by mail-wm1-f43.google.com with SMTP id m22so3233534wml.3 for ; Tue, 05 Feb 2019 03:27:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=LIgFWRdaRcf1wgzF9FAC4scxZDmhf7Hl+Sg1I7woycM=; b=AIsqId4A0nH26vm5sDVuDmE5A1LJjM2gxcXHZHup/d0C8oGEogApMBXaPtDXiwK7wT E7mTZx4/RefKF1fK5CPtpGo5nIsluHWtUuJISB8zZXOu15ky0MUXSa17FMkEtzvzLvJH XdAeuM5JoI4dExV+GOHbVcrLKD4Hh7EI34J1HuUFx2g4WUMU8DmniYBDlrc67c5gTKoB eH5IeZwf7D/QJbtE1flaqDGoquqcPoPFyMFVtazv8Wyxxw3GKCYOG9x0kKoft1rseWi4 Bk7eK1aEzKW9a4Il3mvCuQJ9KDX1/xqOvTkGgih6joeLR48k/zXji8NZLpfuqJjSqveP HQpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LIgFWRdaRcf1wgzF9FAC4scxZDmhf7Hl+Sg1I7woycM=; b=DoIzFE2t+tZw7cKprv1BRB465UN2Q47CK4R8PIkYqlAqrwOrt+qMDUo96uvTNPp0Y6 RNwSdjecRG60Q/q6p76Fsr/ZjnBvFqkFBUuxxg5M7Wg3gfvQVyXiHjhcDxMC6Lu3rRjT Rg17Tem0v8+uRPwQ7ZMBS4rLty5bce2ONgDKFyfWpgDoDL+bC2bNU1kYPQwFn0ojLjyZ H+TcZLd0iviidpnAqLUcJyeSSKdwd74NkmV9LCVLTCkM19XB3/wSIwBP7wcF7Bs6k+7u VeWVHdqCZs8C2u+W57M2H9f2g90kOqFu/LlxdxhGDBPJH2gpkITpFYScR4JqcIr5sRmN srzg== X-Gm-Message-State: AHQUAuZit/FTm22tmkxTHI/Re7dLHCv1AGFEnZEBFu/Tb7aV6TQPODmc h528yx3x1e34ZLzFLHFU63Yk7k6sWaTsuqSThCexozzz X-Google-Smtp-Source: AHgI3Ia+utKstHpKMIcwcUKxMEWHOYBtcnxH/EKMatyYRbGWynvt0aviBBSe3DPPk1Oebec1fiPbWu7aPUNtfpM/3wM= X-Received: by 2002:a1c:e913:: with SMTP id q19mr3399688wmc.55.1549366020377; Tue, 05 Feb 2019 03:27:00 -0800 (PST) MIME-Version: 1.0 From: David Aldrich Date: Tue, 5 Feb 2019 11:26:49 +0000 Message-ID: Subject: Is it possible to specify an external to the same repository? To: users@subversion.apache.org Content-Type: multipart/alternative; boundary="00000000000045acae058123e3ae" --00000000000045acae058123e3ae Content-Type: text/plain; charset="UTF-8" Hi In our embedded projects we have a register interface maintained by our HW team and software that uses that register interface maintained by our SW team. As the interface is constantly changing, we want the software source files to reference a fixed version of the interface. In some projects the register interface and software are in separate repositories. So the software simply references the register interface using an svn external with fixed revision number. In other projects the register interface and software are in the same repository. It is inconvenient to instruct all developers and users to peg specific revisions of the register interface within their working copies. Can we use externals in this situation, or is there another solution? Best regards David --00000000000045acae058123e3ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

In our embedded projects we have a r= egister interface maintained by our HW team and software that uses that reg= ister interface maintained by our SW team.=C2=A0 As the interface is consta= ntly changing, we want the software source files to reference a fixed versi= on of the interface.

In some projects the register= interface and software are in separate repositories. So the software simpl= y references the register interface using an svn external with fixed revisi= on number.

In other projects the register interfac= e and software are in the same repository.=C2=A0 It is inconvenient to inst= ruct all developers and users to peg specific revisions of the register int= erface within their working copies.=C2=A0 Can we use externals in this situ= ation, or is there another solution?

Best regards<= /div>

David

--00000000000045acae058123e3ae--