public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Overlay Git: Feature Branches
Date: Thu, 1 Feb 2018 05:31:02 +0000	[thread overview]
Message-ID: <robbat2-20180201T052752-102205874Z@orbis-terrarum.net> (raw)
In-Reply-To: <CAKkjsY8zza+tCPRO2sLD6jbiXz9h=QPgwQdjK5Qc50b2ZdFOUw@mail.gmail.com>

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.

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?

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136


  reply	other threads:[~2018-02-01  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  2:32 [gentoo-dev] Gentoo Overlay Git: Feature Branches Lucas Ramage
2018-02-01  5:31 ` Robin H. Johnson [this message]
2018-02-01  5:38   ` Georgy Yakovlev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=robbat2-20180201T052752-102205874Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox