From: Philip Boulain <prb@ecs.soton.ac.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae...
Date: Mon, 17 Sep 2007 12:19:58 +0100 [thread overview]
Message-ID: <1190027998.12960.3.camel@panther> (raw)
In-Reply-To: <Pine.LNX.4.64.0709171056560.28586@racer.site>
> > > > DON'T DO THIS KIND OF COMMIT AGAIN, PLEASE.
> > > if we were using git (but you can do it locally anyway), you would not
> > > have these conflicts problems...
> > Maybe... but Savannah uses a CVS frontend, as far as I know...
> Those are excuses.
So is a "you should have used X" argument. It doesn't invalidate the
point that the commit was disruptive, and merely acts as bait for the
grand old "version repository" flamewar.*
> Like whitespace change is breaking your code. Really, I mean, come on.
> Who do think you are kidding?
<flamebait>Python programmers.</flamebait> ;)
LionsPhil
* See also, "if they'd used Perl instead of find/xargs/sed...".
next prev parent reply other threads:[~2007-09-17 11:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 21:08 [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae Thiemo Seufer
2007-09-17 8:08 ` J. Mayer
2007-09-17 8:27 ` Christian MICHON
2007-09-17 9:42 ` J. Mayer
2007-09-17 10:00 ` Johannes Schindelin
2007-09-17 11:19 ` Philip Boulain [this message]
2007-09-17 12:18 ` Christian MICHON
2007-09-17 20:59 ` Andreas Färber
2007-09-17 21:14 ` Luca
2007-09-17 21:46 ` J. Mayer
2007-09-17 22:02 ` Luca
2007-09-18 13:21 ` Thiemo Seufer
2007-09-17 21:30 ` Christian MICHON
2007-09-17 22:47 ` Johannes Schindelin
2007-09-18 16:20 ` Andreas Färber
2007-09-17 9:21 ` Johannes Schindelin
2007-09-17 14:52 ` M. Warner Losh
2007-09-17 13:52 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 23:56 Ben Taylor
2007-09-18 12:49 ` Philip Boulain
2007-09-18 17:05 ` Stefan Weil
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=1190027998.12960.3.camel@panther \
--to=prb@ecs.soton.ac.uk \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.