public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgy Yakovlev <ya@sysdump.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Overlay Git: Feature Branches
Date: Wed, 31 Jan 2018 21:38:29 -0800	[thread overview]
Message-ID: <5723234.YZVCm6kEo9@reaper> (raw)
In-Reply-To: <robbat2-20180201T052752-102205874Z@orbis-terrarum.net>

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?


      reply	other threads:[~2018-02-01  5:38 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
2018-02-01  5:38   ` Georgy Yakovlev [this message]

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=5723234.YZVCm6kEo9@reaper \
    --to=ya@sysdump.net \
    --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