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] Re: How to speed up maintenance and other Gentoo work?
Date: Sat, 7 Mar 2009 18:29:08 -0800	[thread overview]
Message-ID: <20090308022908.GB16405@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <81bfc67a0903071657i13e7e56ajcffb039e2a4e290b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Sat, Mar 07, 2009 at 07:57:02PM -0500, Caleb Cushing wrote:
> On Sat, Mar 7, 2009 at 2:27 PM, Alec Warner <antarus@gentoo.org> wrote:
> > People are working on the whole 'replace cvs with git' thing on the
> > gentoo-scm list.
> I'm supposedly on that list and I haven't gotten a message all week?
> is it low traffic? or do I have a subscription/other problem.
It's fairly low traffic.

The last discussion was just under 2 weeks ago, was about how Manifests
would need to be changed to cut down on merge conflicts. The last
proposal on that was to consider a form of slim Manifest for developers
only (it would still be a full form going to rsync), where objects in
git were not explicitly tracked in the Manifest, but rather but signed
commits (not tags), as their checksums were tracked by the DVCS anyway.

Additionally, there is this pending item on a Git resource usage bug
that hurts badly during the initial clone:
http://archives.gentoo.org/gentoo-scm/msg_df7c98ec7d2e313856bec31769df407f.xml

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]

  reply	other threads:[~2009-03-08  6:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  2:01 [gentoo-dev] How to speed up maintenance and other Gentoo work? Mart Raudsepp
2009-03-04  2:24 ` Mike Frysinger
2009-03-04  5:37   ` Donnie Berkholz
2009-03-04  2:26 ` Peter Alfredsen
2009-03-04  2:51   ` Olivier Crête
2009-03-04  4:54     ` Josh Saddler
2009-03-04  5:36   ` Donnie Berkholz
2009-03-04 12:50 ` [gentoo-dev] " Nicolas Sebrecht
2009-03-07  7:22   ` Caleb Cushing
2009-03-07 11:21     ` Nicolas Sebrecht
2009-03-07 19:27     ` Alec Warner
2009-03-08  0:57       ` Caleb Cushing
2009-03-08  2:29         ` Robin H. Johnson [this message]
2009-03-08 14:10           ` Nicolas Sebrecht
2009-03-06 19:02 ` [gentoo-dev] " Petteri Räty
2009-03-07  1:44 ` [gentoo-dev] " Ryan Hill
2009-03-07  3:08   ` Duncan
2009-03-13  8:24 ` [gentoo-dev] " Thilo Bangert
2009-03-13 12:44   ` Grant Goodyear

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=20090308022908.GB16405@curie-int.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