Johannes Sixt wrote:
>Thiago Macieira schrieb:
>> Ian Monroe wrote:
* the unresolved issue of accountability
>>>
>>> This is the main issue I see. I hear there are solutions though?
>>
>> We have to see whether Git notes solves the problem.
>
>I still don't see a need for this. Just build a n
Ian Monroe schrieb:
> On Sat, Jan 17, 2009 at 5:17 PM, Thiago Macieira wrote:
>> * should we use a patch-submission-and-review system? (probably not)
>
> no.
Don't throw patch submission and review into the same bucket. I can
understand that you want to dispense with patch submission. But if KD
Ian Monroe (2009-01-18 10:29 -0600) wrote:
> On Sun, Jan 18, 2009 at 10:15 AM, Robert Wohlrab wrote:
>> Please note that git tracks everything by its sha1. So rebasing a
>> branch will change its sha1's and you will get the same stuff as
>> above. So I would say nobody should have forced push r
Ian Monroe wrote:
>> Beyond that, I think all the other issues can be resolved "in conference"
>> with the Amarok developers. I know Thiago isn't volunteering, but I
>> *think* there are others on the list that may have time to discuss (and
>> possibly implement) this. I work a normal, US-Central
Thiago Macieira schrieb:
> Ian Monroe wrote:
>>> * the unresolved issue of accountability
>> This is the main issue I see. I hear there are solutions though?
>
> We have to see whether Git notes solves the problem.
I still don't see a need for this. Just build a network of trust (or
better, make
Ian Monroe wrote:
>You don't see any benefit to having a project like Amarok try things
> out?
Of course I do.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Des
Ian Monroe wrote:
>> SVN externs are not a problem. They just die. Get rid of them right
>> now, on SVN (they are hurting you now because you're using git-svn).
>> SVN and Git users will thank you.
>
>Actually we already got rid of them. I was confused. :)
>
>Still we need to have this info recorde
On Sun, Jan 18, 2009 at 11:21 AM, Thiago Macieira wrote:
> Ian Monroe wrote:
>>> I see both reasons as valid. However, I thought being "part of KDE"
>>> meant being maintained under the same source control. That said,
>>> Amarok survived fine being not "part of KDE" in the past and I think
>>> i
On Sunday 18 January 2009 20:21:15 Thiago Macieira wrote:
> I, for one, would advocate for kdelibs to switch to Git[*]. That way, we
> force everyone to start using it and learning it.
Great idea (about learning)! As I feel that I know some git basics, but I
really miss the general flow feeling of
Ian Monroe wrote:
>> I see both reasons as valid. However, I thought being "part of KDE"
>> meant being maintained under the same source control. That said,
>> Amarok survived fine being not "part of KDE" in the past and I think
>> it could flourish there again.
>
>Amarok has been in KDE SVN sinc
On Sun, Jan 18, 2009 at 7:58 AM, Boyd Stephen Smith Jr.
wrote:
> On Saturday 17 January 2009, Casey Link wrote
> about 'Re: [Kde-scm-interest] On Amarok Switching to Git':
>>Leo and I brought this topic up at a break a few minutes ago during
>>Camp KDE, and immediately Chani and Thomas jumped in.
On Sun, Jan 18, 2009 at 10:15 AM, Robert Wohlrab wrote:
> On Sunday 18 January 2009 16:52:18 Ian Monroe wrote:
> [..]
>> > * who will have push rights? To which branches? Who can create branches?
>> > Which branches/repos will allow force-pushes?
>> Well everyone will have push rights. I don't kn
On Sunday 18 January 2009 16:52:18 Ian Monroe wrote:
[..]
> > * who will have push rights? To which branches? Who can create branches?
> > Which branches/repos will allow force-pushes?
> Well everyone will have push rights. I don't know what a force push is.
Normally you can only push if you do a
On Sat, Jan 17, 2009 at 5:17 PM, Thiago Macieira wrote:
> Ian Monroe wrote:
>>* Scripty. Its somewhat of a mystery where it is and how this thing
>>works. :) So it just needs to clone the central git repo, and perhaps
>>use a stable branch in the future. It should commit the translation
>>files ba
A Dissabte 17 Gener 2009, Ian Monroe va escriure:
> So most Amarok devs use git-svn now, and there's a growing consensus
> that switching to Git would make life easier. So I'd like to request
> assistance and pointers on how to actually go about doing this.
>
> I understand from reading the archive
On Saturday 17 January 2009, Casey Link wrote
about 'Re: [Kde-scm-interest] On Amarok Switching to Git':
>Leo and I brought this topic up at a break a few minutes ago during
>Camp KDE, and immediately Chani and Thomas jumped in. We started
>discussing technical and social hurdles that have to be
Hello,
Leo and I brought this topic up at a break a few minutes ago during
Camp KDE, and immediately Chani and Thomas jumped in. We started
discussing technical and social hurdles that have to be crossed before
all of KDE can ditch svn for good.
The more I think about it, the more I like the idea
17 matches
Mail list logo
