From: Seemant Kulleen <seemantk@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council / Git Migration Agenda
Date: Mon, 6 Oct 2014 01:42:12 -0700 [thread overview]
Message-ID: <CAJEWDoVdUR4z5PxVE0tTLm2JLr4VE_wF6MipLjc-BkEnERAapA@mail.gmail.com> (raw)
In-Reply-To: <21554.11562.674143.286256@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
I guess it boils down to priority. History becomes inconvenient to trace
at some point. That's true for most human things...nothing is perfect.
seemantk empathic design
http://seemantk.com
On Oct 5, 2014 10:48 PM, "Ulrich Mueller" <ulm@gentoo.org> wrote:
> >>>>> On Sun, 5 Oct 2014, Seemant Kulleen wrote:
>
> > Libraries don't have to be sad. If the history remains in a CVS
> > repo isn't that the perfect home for it in the museum of gentoo's
> > history?
>
> Having the complete history in a single repository would be much
> preferable, even if that history is not perfect.
>
> It's annoying if you search for the point when some change was
> performed, only to find that the repo's history doesn't reach back
> that far. I've had this issue e.g. with the Portage repository whose
> history was cut off at some point. Having to change tools (from git to
> cvs) in addition doesn't make it better.
>
> Ulrich
>
[-- Attachment #2: Type: text/html, Size: 1331 bytes --]
next prev parent reply other threads:[~2014-10-06 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 0:00 [gentoo-project] Council / Git Migration Agenda Rich Freeman
2014-10-04 7:15 ` Michał Górny
2014-10-05 8:18 ` Dirkjan Ochtman
2014-10-05 9:33 ` Michał Górny
2014-10-06 1:27 ` hasufell
2014-10-06 2:50 ` Seemant Kulleen
2014-10-06 5:48 ` Ulrich Mueller
2014-10-06 8:42 ` Seemant Kulleen [this message]
2014-10-06 8:48 ` Michał Górny
2014-10-07 7:57 ` Dirkjan Ochtman
2014-10-07 8:07 ` [gentoo-scm] " Michał Górny
2014-10-07 8:20 ` Ulrich Mueller
2014-10-07 8:26 ` Michał Górny
2014-10-07 10:58 ` Rich Freeman
2014-10-07 11:00 ` Anthony G. Basile
2014-10-07 11:09 ` Rich Freeman
2014-10-09 19:33 ` Tom Wijsman
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=CAJEWDoVdUR4z5PxVE0tTLm2JLr4VE_wF6MipLjc-BkEnERAapA@mail.gmail.com \
--to=seemantk@gmail.com \
--cc=gentoo-project@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