Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-scm
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: "Robin H. Johnson" <robbat2@g.o>
From: Caleb Cushing <xenoterracide@...>
Subject: Re: Splitting gentoo-x86 repository for easier consumption
Date: Sun, 12 Apr 2009 01:14:10 -0400
On Sat, Apr 11, 2009 at 2:14 PM, Robin H. Johnson <robbat2@g.o> wrote:
> Ah, yes, we could possibly exclude all lines other than DIST during the
> conversion. It would mean post-processing is needed to use the tree
> anyway, but that shouldn't be a problem.

if you aren't going to use git as a distribution mechanism is there a
point to storing any manifests in the tree? why not just add Manifest
to .gitignore? otherwise to make it work with rsync you'll still have
to gen the full manifest each time.

-- 
Caleb Cushing

http://xenoterracide.blogspot.com


Replies:
Re: Splitting gentoo-x86 repository for easier consumption
-- Robin H. Johnson
References:
Splitting gentoo-x86 repository for easier consumption
-- Maciej Mrozowski
Re: Splitting gentoo-x86 repository for easier consumption
-- Caleb Cushing
Re: Splitting gentoo-x86 repository for easier consumption
-- Robin H. Johnson
Re: Splitting gentoo-x86 repository for easier consumption
-- Caleb Cushing
Re: Splitting gentoo-x86 repository for easier consumption
-- Robin H. Johnson
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Splitting gentoo-x86 repository for easier consumption
Next by thread:
Re: Splitting gentoo-x86 repository for easier consumption
Previous by date:
Re: Status report, 2009/04/10
Next by date:
Re: Splitting gentoo-x86 repository for easier consumption


Updated Jun 17, 2009

Summary: Archive of the gentoo-scm mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.