All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Reverting recent openmoko commit
Date: Mon, 27 Oct 2008 12:13:40 +0100	[thread overview]
Message-ID: <4905A264.9050509@klever.net> (raw)
In-Reply-To: <ge211u$h4r$1@ger.gmane.org>

What I fail to see is how does reverting commits improve history.

What I do see is that the reverting commits do not adhere to the policy 
in question ;-)

Love,
H

Koen Kooi wrote:
> Hi,
> 
> I'm going to revert all recent openmoko commits till these guys learn 
> how to write a commit message. You have been warned before.
> 
> In case you missed it, this wrong:
> 
> [foo] something
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  parent reply	other threads:[~2008-10-27 11:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 15:06 Reverting recent openmoko commit Koen Kooi
2008-10-26 15:39 ` Michael 'Mickey' Lauer
2008-10-27  9:10 ` Phil Blundell
2008-10-27 10:37   ` Philip Balister
2008-10-27 12:45     ` Holger Freyther
2008-10-27 13:03       ` Michael 'Mickey' Lauer
2008-10-27 16:09         ` Philip Balister
2008-10-27 13:12       ` Michael Krelin
2008-10-27 10:39   ` Philip Balister
2008-10-27 11:13 ` Michael Krelin [this message]
2008-10-27 11:30   ` Policies vs. Guidelines vs. Requirements (was: Reverting recent openmoko commit) Michael 'Mickey' Lauer
2008-10-27 11:46     ` Policies vs. Guidelines vs. Requirements Michael Krelin

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=4905A264.9050509@klever.net \
    --to=hacker@klever.net \
    --cc=openembedded-devel@lists.openembedded.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.