From: Andrew Cowie <andrew@operationaldynamics.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla usage by gentoo-java's doing migration work
Date: Sat, 24 Jun 2006 12:25:10 +1000 [thread overview]
Message-ID: <1151115910.8047.16.camel@procyon.operationaldynamics.com> (raw)
In-Reply-To: <1151072899.18759.88.camel@cgianelloni.nuvox.net>
On Fri, 2006-06-23 at 10:28 -0400, Chris Gianelloni wrote:
> Now, the java team is an official Gentoo project...
And even more pertinent (and a point that got lost in all this, sadly):
The gentoo-java's migration effort is NOT an overlay in the sense that
breakmygentoo or sunrise are. It is merely a branch.
If we were using a distributed version control tool, or even subversion
for the tree rather than good ol' CVS, I'm quite sure that all of their
work would have been done on a branch inside the primary tree's revision
control system, rather than externally in a (whoa) subversion repo of
their own.
Oh well. I just hope this doesn't affect nichoj and karltk and the
others too badly as they finish up their year+ of effort to complete
this branch and merge it back into HEAD.
AfC
Sydney
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-24 3:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 0:05 [gentoo-dev] sunrise, a temporary compromise Mike Doty
2006-06-23 4:49 ` Donnie Berkholz
2006-06-23 6:12 ` Stuart Herbert
2006-06-23 7:22 ` Anders Hellgren
2006-06-23 8:49 ` [gentoo-dev] Bugzilla usage for overlays' projects [was: sunrise, a temporary compromise] Jakub Moc
2006-06-23 11:50 ` Joshua Nichols
2006-06-23 12:18 ` [gentoo-dev] Bugzilla usage by gentoo-java's doing migration work Andrew Cowie
2006-06-23 12:50 ` Patrick Lauer
2006-06-23 13:35 ` Stephen P. Becker
2006-06-23 13:50 ` Jakub Moc
2006-06-23 14:28 ` Chris Gianelloni
2006-06-23 14:54 ` Jakub Moc
2006-06-24 2:25 ` Andrew Cowie [this message]
2006-06-24 4:07 ` James Potts
2006-06-24 11:14 ` Wernfried Haas
2006-06-24 11:21 ` Simon Stelling
2006-06-24 14:52 ` James Potts
2006-06-25 7:41 ` Simon Stelling
2006-06-25 18:36 ` Donnie Berkholz
2006-06-26 19:23 ` Chris Gianelloni
2006-06-25 5:10 ` Mike Frysinger
2006-06-23 14:20 ` Joshua Nichols
2006-06-23 14:40 ` Henrik Brix Andersen
2006-06-23 16:14 ` Patrick Lauer
2006-06-23 16:37 ` Ciaran McCreesh
2006-06-24 2:38 ` Lance Albertson
2006-06-24 8:56 ` Patrick Lauer
2006-06-24 10:40 ` Luca Barbato
2006-06-24 14:25 ` Lance Albertson
2006-06-23 14:17 ` [gentoo-dev] Bugzilla usage for overlays' projects [was: sunrise, a temporary compromise] Donnie Berkholz
2006-06-23 12:43 ` Seemant Kulleen
2006-06-23 10:09 ` Alec Warner
2006-06-23 14:23 ` Donnie Berkholz
2006-06-23 16:59 ` Mike Doty
2006-06-23 13:00 ` Jakub Moc
2006-06-23 13:09 ` Harald van Dijk
2006-06-23 14:27 ` Ciaran McCreesh
2006-06-23 14:58 ` Harald van Dijk
2006-06-23 15:11 ` Seemant Kulleen
2006-06-23 16:07 ` Harald van Dijk
2006-06-23 17:33 ` Seemant Kulleen
2006-06-23 18:19 ` Harald van Dijk
2006-06-23 15:14 ` Seemant Kulleen
2006-06-23 13:26 ` Andrew Gaffney
2006-06-23 14:15 ` George Shapovalov
2006-06-23 13:14 ` Alec Warner
2006-06-23 13:11 ` [gentoo-dev] sunrise, a temporary compromise Mike Doty
2006-06-23 14:21 ` Donnie Berkholz
2006-06-23 16:14 ` Mike Doty
2006-06-23 13:04 ` Mike Doty
2006-06-23 13:58 ` Ned Ludd
2006-06-23 14:15 ` Chris Gianelloni
2006-06-23 18:39 ` Seemant Kulleen
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=1151115910.8047.16.camel@procyon.operationaldynamics.com \
--to=andrew@operationaldynamics.com \
--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