Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/dbus
Date: Sun, 01 Feb 2009 07:31:05 +0100	[thread overview]
Message-ID: <87zlh6is7q.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090201055814.GA8215@cloud.net.au> (Hamish Moffatt's message of "Sun\, 1 Feb 2009 16\:58\:14 +1100")

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

 >> dbus: revert r25194 (Unbreak Peters 'fixes' to dbus for a second time)
 >> 
 >> It was a bogus revert.

 Hamish> Are we having fun yet?

Yeah, I know it's silly.

I know it's mainly a social problem, but to me it again shows the need
from moving from the svn code ghetto approach to git's approach with
patches to the list and finally pull requests to the maintainer.

E.G. get the code reviewed BEFORE it gets into the tree, and not
afterwards.

But let's discuss this after the release.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-02-01  6:31 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 22:53 [Buildroot] svn commit: trunk/buildroot/package/dbus jacmet at uclibc.org
2009-02-01  5:58 ` Hamish Moffatt
2009-02-01  6:31   ` Peter Korsgaard [this message]
2009-02-01 10:58     ` Ulf Samuelsson
2009-02-01 13:17       ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-02-24 11:13 jacmet at uclibc.org
2009-02-22 20:12 jacmet at uclibc.org
2009-01-31 21:01 ulf at uclibc.org
2009-01-31 18:39 jacmet at uclibc.org
2009-01-31 20:52 ` Ulf Samuelsson
2009-01-31 21:20   ` Peter Korsgaard
2009-01-31 21:55     ` Ulf Samuelsson
2009-01-31 22:26       ` Peter Korsgaard
2009-01-31 12:02 ulf at uclibc.org
2009-01-31 13:09 ` Peter Korsgaard
2009-01-30 13:54 jacmet at uclibc.org
2009-01-25 20:55 ulf at uclibc.org
2009-01-25 21:00 ` Peter Korsgaard
2009-01-25 23:31   ` Ulf Samuelsson
2009-01-26  6:02     ` Peter Korsgaard
2008-06-20 21:45 jacmet at uclibc.org
2008-06-15 20:20 jacmet at uclibc.org
2008-04-06 13:33 ulf at uclibc.org
2008-03-31 19:36 jacmet at uclibc.org
2008-03-12 14:51 ninevoltz at uclibc.org
2008-03-06 18:46 ninevoltz at uclibc.org
2008-03-04 12:19 jacmet at uclibc.org
2008-01-30 13:57 vanokuten at uclibc.org
2007-11-26 15:47 jacmet at uclibc.org
2007-11-25 23:30 ulf at uclibc.org
2007-11-25 14:49 ulf at uclibc.org
2007-11-23 15:46 jacmet at uclibc.org
2007-11-23 13:21 jacmet at uclibc.org
2007-11-23 11:44 jacmet at uclibc.org
2007-11-23 11:43 jacmet at uclibc.org
2007-11-23 12:50 ` Ivan Kuten
2007-11-23 12:33   ` Peter Korsgaard
2007-11-23 10:00 jacmet at uclibc.org
2007-11-23  9:46 jacmet at uclibc.org
2007-11-22 17:12 jacmet at uclibc.org
2007-08-21 12:09 aldot at uclibc.org
2007-07-17 15:19 ulf at uclibc.org
2007-07-08 13:20 aldot at uclibc.org
2007-01-15 16:02 aldot at uclibc.org

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=87zlh6is7q.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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