linux-kernel - Re: Linux 2.6.16.26

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0607151439020.5623@g5.osdl.org>
Date:	Sat, 15 Jul 2006 14:40:30 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Willy Tarreau <w@....eu>
cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...l.org>, stable@...nel.org
Subject: Re: Linux 2.6.16.26



On Sat, 15 Jul 2006, Willy Tarreau wrote:
> 
> You would need to git-reset then git-commit

Actually, these days we suggest doing

	git commit --amend

instead to change the top commit if you mis-type something or find a 
problem.

But, as you point out:

>					 but it's a little bit dirty
> and my annoy the users who will have already fetched your tree.

Indeed. Something that has already been exported should _not_ be amended, 
because it generates a whole new commit, and people who have already 
gotten the old one would be unhappy.

		Linus
-
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/