linux-kernel - Re: [git pull] core/softirq for v2.6.27

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 14 Jul 2008 20:23:26 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [git pull] core/softirq for v2.6.27


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Mon, 14 Jul 2008, Ingo Molnar wrote:
> > 
> > /me suggests git-log-addendum feature to amend commit logs after the
> >     fact, without changing any of the code :-)
> 
> It's called "git commit --amend".

yeah - and i use that for general development meanwhile: i just 
commit the draft code in small steps (appending it to the commit via
git commit --amend), then i test it and amend it with a final commit
log in the end.

I use that method instead of doing development via uncommitted changes 
in the git index, because that way:

 - I see the under-development change in a form close to how other
   people see it (as a commit)

 - I can switch branches during development

 - It's sure that changes are not lost

 - I can distribute my half-done commits to my testboxes (internally i
   use a hierarchy of Git repos on testboxes to automatically propagate
   changes)

Once it's pushed out publicly into a persistent branch it cannot be 
touched anymore.

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