On Friday 13 November 2009 08:03:27 Ian Monroe wrote:
> 2009/11/12 Michael Pyne :
> > On Thursday 12 November 2009 14:46:47 Boudewijn Rempt wrote:
> >> > On Thursday 12. November 2009 19.05.25 Boudewijn Rempt wrote:
> >> > >-> write a script to clone, update and build everything, like
> >>
On Sat, Nov 14, 2009 at 12:03:20AM +0100, Thomas Zander wrote:
> On Friday 13. November 2009 23.43.05 Oswald Buddenhagen wrote:
> > anyway, if you don't believe me, [...]
>
> We have done all the benchmarks and research, and we reached a quite
> different conclusion from yours.
>
yes? and where a
On Friday 13. November 2009 23.43.05 Oswald Buddenhagen wrote:
> anyway, if you don't believe me, just take some other random projects
> with a long history or create some artificial benchmarks. in particular,
> anything which has multimedia data in it will have exploding .git
> directories (and re
On Fri, Nov 13, 2009 at 04:10:36PM -0600, Ian Monroe wrote:
> On Fri, Nov 13, 2009 at 3:15 PM, Oswald Buddenhagen wrote:
> > have you ever run 'du' on the .git directory on the git-svn import of
> > kdebase/workspace?
>
> Git-svn has a lot of overhead that we won't have.
>
and what would that ove
On Fri, Nov 13, 2009 at 3:15 PM, Oswald Buddenhagen wrote:
> On Fri, Nov 13, 2009 at 08:54:22PM +0100, Thomas Zander wrote:
>> On Friday 13. November 2009 11.51.04 Oswald Buddenhagen wrote:
>> > and before you ask (again): i have no resources to work on it. but i
>> > sure will have the resources
On Fri, Nov 13, 2009 at 08:54:22PM +0100, Thomas Zander wrote:
> On Friday 13. November 2009 11.51.04 Oswald Buddenhagen wrote:
> > and before you ask (again): i have no resources to work on it. but i
> > sure will have the resources to start a revolution if a system which
> > introduces major regr
On Friday 13. November 2009 11.51.04 Oswald Buddenhagen wrote:
> On Thu, Nov 12, 2009 at 08:23:54PM +0100, Thomas Zander wrote:
> > On Thursday 12. November 2009 20.02.44 Oswald Buddenhagen wrote:
> > > disadvantages of big repos:
> > > - huge clones for everybody
> >
> > "Huge" is a bit inaccurate
On Fri, Nov 13, 2009 at 2:51 AM, Oswald Buddenhagen wrote:
> like hundreds of megabytes? if i want just kcalc, why should i have to
> check out everything which happens to have been lumped into the same
> repository, including it's entire history? kde's idea of "modules" was
> always one of the b
Ian Monroe wrote:
> Which is why I like my simple flat-file log idea (a log of commit
> hash, user id, maybe time). It doesn't open up any privacy issues
> (since the info is already public) and would solve the problem by
> using the commit hash, which is a nice security feature of git.
You still
On Fri, Nov 13, 2009 at 8:28 AM, Johan Sørensen wrote:
> On Fri, Nov 13, 2009 at 8:01 AM, Boudewijn Rempt wrote:
>> After all, once the e.V. can have the backups of the database, as discussed
>> already, the rest is a simple matter of writing a policy document and
>> pointing
>> external contrib
Em Sexta-feira 13 Novembro 2009, às 15:28:35, você escreveu:
> As for the actual topic of the thread; aren't you trying to find a
> cure for a symptom here? Even if you knew exactly who committed it,
> the code would still be bad and/or evil. So either the ring of people
> you trust with commit acc
On Fri, Nov 13, 2009 at 8:01 AM, Boudewijn Rempt wrote:
> After all, once the e.V. can have the backups of the database, as discussed
> already, the rest is a simple matter of writing a policy document and pointing
> external contributors at it.
OK, I'm not sure exactly how this turned into a com
On Friday 13 November 2009, Thomas Zander wrote:
> As the meeting minutes show a TODO list I'd like to suggest we look at the
> 'accountability' thread I started with a mail on 31.07.2008 15.07
> "Accountability, concrete suggestion" and not let that one slip through the
> cracks.
It can be put on
On Thu, Nov 12, 2009 at 5:54 PM, Thomas Zander wrote:
> As the meeting minutes show a TODO list I'd like to suggest we look at the
> 'accountability' thread I started with a mail on 31.07.2008 15.07
> "Accountability, concrete suggestion" and not let that one slip through the
> cracks.
>
> We need
2009/11/12 Michael Pyne :
> On Thursday 12 November 2009 14:46:47 Boudewijn Rempt wrote:
>> > On Thursday 12. November 2009 19.05.25 Boudewijn Rempt wrote:
>> > > -> write a script to clone, update and build everything, like
>> > > kde-svn (TASK: Morice).=
>> >
>> > What does this mean?
>>
>
On Thu, Nov 12, 2009 at 08:23:54PM +0100, Thomas Zander wrote:
> On Thursday 12. November 2009 20.02.44 Oswald Buddenhagen wrote:
> > disadvantages of big repos:
> > - huge clones for everybody
>
> "Huge" is a bit inaccurate, please provide numbers. (See ML history).
>
like hundreds of megabytes?
On Fri, Nov 13, 2009 at 10:48 AM, Bart Cerneels wrote:
> Perhaps its possible to prevent the whole issue thanks to some
> features of gitorious?
>
> Gitorious has support for aliases: email addresses in commits
> associated with your account.
> Is it possible to only allow a push when all email ad
On Fri, Nov 13, 2009 at 00:54, Thomas Zander wrote:
> As the meeting minutes show a TODO list I'd like to suggest we look at the
> 'accountability' thread I started with a mail on 31.07.2008 15.07
> "Accountability, concrete suggestion" and not let that one slip through the
> cracks.
>
> We need s
18 matches
Mail list logo
