From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B180A1382C5 for ; Thu, 1 Feb 2018 05:38:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A502BE0A53; Thu, 1 Feb 2018 05:38:31 +0000 (UTC) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 545C5E09D9 for ; Thu, 1 Feb 2018 05:38:31 +0000 (UTC) Received: by mail-io0-x22a.google.com with SMTP id c17so17813914iod.1 for ; Wed, 31 Jan 2018 21:38:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sysdump.net; s=google; h=from:to:subject:date:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=Qa+W73KM7Lmu5wohkANQ4Q3mhfxX92APHVaF3q07wkU=; b=Ju8KsTxMMNJ1rNU1o81pEnwdi8rOaNZUujd+RdQRwYGnmKvvfgefDS0Mxx750g9yS9 cZYfR+ujG00OKvaPIwGt36/nqzzPrm8CgUWwH/hJOMBllzQdXwlJkStbEKdOkCV9sBbz /Nl//+UvzO4SrQJMyNI7D3DGjcoKYwMiaNAu1WQcgnN4NdO2bmfl+Gglj1xorcjuZy2J jjbGMm2smz9dH1h+KQjjIccUdzOQ8Q6wSjloXy3Z2O5YU3a8osBeS3/jkpQoDML3HHCe 1KmORqpYv5ux1sqfJXosdKg28v5zsxQXCTDZzyYymSaEEPo9mCiwqxWnvAfVO1f3STnU yU1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Qa+W73KM7Lmu5wohkANQ4Q3mhfxX92APHVaF3q07wkU=; b=Vltyid6p7WWG7bNsyMPI1akGMOIENtFQu8FqzlQmMmE6g0xi1/QMarZDurhs3mlAmc XOq24wZTujRUs7QQjdmntaO4xv3Tcok/eg8gwnHwflLVzXeqndDWsQLEE7lvFZDwTwaW o9HSPkLaDifnTs6cSjZLZVV95VQMuRKgjsQihcycpz8wenRAhD1MLlioGsCsA/CInvIW Sti+ixKPCoSMFtuD9uYIrxvY3s04KWvo1i9Q/2FRrwgDLeF4dl+aesiC/C7oo5MMBOLY YWMscpr0OX9zj1r5mzAJOC1eNlupft2qJ8SKOBABx59dNYLmRLk/JqjhNXwZn9gHjXN4 AuBA== X-Gm-Message-State: AKwxyteQpDidH0LofIWAYfawWjgLOx0sE30DZrFnzZJBS3SPSWz+Dvf+ Kr1AjwDw5LBGzhp+DcGieIdAr3wVBGA= X-Google-Smtp-Source: AH8x2253snq4N10qvaEQ/rVqSPYli1eam/jsK1tdEs3kuvZIuQDKSsy0KPkkOvhlpBXi6yHp3Bar6g== X-Received: by 10.107.7.198 with SMTP id g67mr35699699ioi.271.1517463510342; Wed, 31 Jan 2018 21:38:30 -0800 (PST) Received: from reaper.localnet (cpe-75-83-91-39.socal.res.rr.com. [75.83.91.39]) by smtp.gmail.com with ESMTPSA id v11sm913526itf.6.2018.01.31.21.38.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 21:38:29 -0800 (PST) From: Georgy Yakovlev To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Gentoo Overlay Git: Feature Branches Date: Wed, 31 Jan 2018 21:38:29 -0800 Message-ID: <5723234.YZVCm6kEo9@reaper> In-Reply-To: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 48d02b63-785d-47c5-9392-1acafadc400a X-Archives-Hash: 73d588b395b42b62faf6c3b5c46c3bba On Wednesday, January 31, 2018 9:31:02 PM PST Robin H. Johnson wrote: > On Wed, Jan 31, 2018 at 09:32:39PM -0500, Lucas Ramage wrote: > > Hello, > > > > Is there a way to specify a branch in repos.conf/overlay_name.conf? > > The source of Portage's pym/portage/sync/modules/git/git.py contains > this comment: > def update(self): > ''' Update existing git repository, and ignore the syncuri. We are > going to trust the user and assume that the user is in the branch > that he/she wants updated. We'll let the user manage branches with > git directly. > ''' > > To that end, I think the answer is no. > I answered the initial question off-list, copying the list this time. It's actually it's possible. sync-git-clone-extra-opts = -b branchname will clone only single branch and will create a shallow clone. all the future syncs will pull this branch as explained above in the source code snippet. > If this were to change, there are a bunch of questions that would need > agreement in how they are answered: - if the repo's remote URI has changed, > should we update the git checkout's remote URI from sync-uri? (what if > there are multiple remotes in the checkout?) - if the repo's branch has > changed in the config, should we update the checkout's branch?