All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Bryan Wu <cooloney@kernel.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] kallsyms: Nuke all ChangeLog, this should be logged by git
Date: Mon, 28 Apr 2008 20:02:09 +0100	[thread overview]
Message-ID: <48161F31.6010605@grupopie.com> (raw)
In-Reply-To: <1209119299-27894-3-git-send-email-cooloney@kernel.org>

Bryan Wu wrote:
> Pointed out by Paulo:
> "When I wrote this initially, it was a mistake to add a Changelog
> in the first place, but I didn't know better at the time.
> 
> If you're going to make changes to this file, please remove all the
> Changelog, instead of adding more entries to it. The "Changelog"
> should be kept by the version control system, and not the source code itself."
> 
> Cc: Paulo Marques <pmarques@grupopie.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
> ---

Signed-off-by: Paulo Marques <pmarques@grupopie.com>

-- 
Paulo Marques - www.grupopie.com

"God is love. Love is blind. Ray Charles is blind. Ray Charles is God."

  reply	other threads:[~2008-04-28 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 10:28 [PATCH 0/2] kallsyms updates for Blackfin Bryan Wu
2008-04-25 10:28 ` [PATCH 1/2] kallsyms: Allow kernel symbols in L1 to be found in Blackfin architecture Bryan Wu
2008-04-28 19:01   ` Paulo Marques
2008-04-29 22:00   ` Andrew Morton
2008-04-30 13:51     ` Robin Getz
2008-04-30 15:43       ` Andrew Morton
2008-04-25 10:28 ` [PATCH 2/2] kallsyms: Nuke all ChangeLog, this should be logged by git Bryan Wu
2008-04-28 19:02   ` Paulo Marques [this message]
2008-04-28 18:59 ` [PATCH 0/2] kallsyms updates for Blackfin Paulo Marques

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=48161F31.6010605@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=akpm@linux-foundation.org \
    --cc=cooloney@kernel.org \
    --cc=linux-kernel@vger.kernel.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.