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: gentoo-scm@g.o
From: Thilo Bangert <bangert@g.o>
Subject: Git migration Tracker bug
Date: Fri, 20 Aug 2010 01:13:31 +0200
Hi, 

I was just about to start another, really useless "whats the status" mail 
to gentoo-scm. Then it occured to me, that it may be more productive to 
create a git migration tracker bug, with a bug for each of the action 
items and investigations etc. attached. Perhaps that would give those 
interested in the current progress a better view of whats going on...

Checking whether such a bug already existed i found
http://bugs.gentoo.org/show_bug.cgi?id=261380
which is about thin manifest when using git.

In comment #5
http://bugs.gentoo.org/show_bug.cgi?id=261380#c5
robbat2 says to keep all discussions on this list, in order to not loose a 
picture of the broad view.
Perhaps these two can both be implemented: keeping discussion on list, but 
statuses in bugs.

What do people think?

I have created a preliminary tracker bug at
http://bugs.gentoo.org/show_bug.cgi?id=333531

feel free to add bugs to it, if this is something you find usefull. if 
there are no (violent) objections, i would create corresponding child bugs 
with the issues covered so far some time tomorrow.
thanks

good night
Thilo
Attachment:
signature.asc (This is a digitally signed message part.)
Replies:
Re: Git migration Tracker bug
-- Thilo Bangert
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
GIT->rsync
Next by thread:
Re: Git migration Tracker bug
Previous by date:
Re: Status
Next by date:
Re: Git migration Tracker bug


Updated May 23, 2012

Summary: Archive of the gentoo-scm mailing list.

Donate to support our development efforts.

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