| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20090820141349.9967b275.akpm@linux-foundation.org>
Date: Thu, 20 Aug 2009 14:13:49 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Paul Menage <menage@...gle.com>
Cc: bblum@...rew.cmu.edu, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org
Subject: Re: [PATCH 1/8] Revert commit
8827c288feb7810185aa7c2e37537202fc709869
On Tue, 18 Aug 2009 16:58:12 -0700
Paul Menage <menage@...gle.com> wrote:
> Revert commit 8827c288feb7810185aa7c2e37537202fc709869
>
> This is in preparation for some clashing cgroups changes that subsume
> the original commit's functionaliy.
Please don't refer to commits via their bare hash number.
This commit actually has a different hash in my tree:
commit 096b7fe012d66ed55e98bc8022405ede0cc80e96
Author: Li Zefan <lizf@...fujitsu.com>
AuthorDate: Wed Jul 29 15:04:04 2009 -0700
Commit: Linus Torvalds <torvalds@...ux-foundation.org>
CommitDate: Wed Jul 29 19:10:35 2009 -0700
cgroups: fix pid namespace bug
And it will definitely have a different hash in linux-next, -stable,
distro trees, etc.
So the conventional way of referring to a commit within a changelog is
096b7fe012d66ed55e98bc8022405ede0cc80e96 ("cgroups: fix pid namespace bug")
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists