public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [git pull] core/softirq for v2.6.27
Date: Mon, 14 Jul 2008 20:23:26 +0200	[thread overview]
Message-ID: <20080714182326.GA15243@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0807141011260.3305@woody.linux-foundation.org>


* Linus Torvalds <torvalds@linux-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

      reply	other threads:[~2008-07-14 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 14:42 [git pull] core/softirq for v2.6.27 Ingo Molnar
2008-07-14 16:22 ` Andrew Morton
2008-07-14 16:31   ` Ingo Molnar
2008-07-14 16:44     ` Andrew Morton
2008-07-14 16:48       ` Ingo Molnar
2008-07-14 17:13         ` Linus Torvalds
2008-07-14 18:23           ` Ingo Molnar [this message]

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=20080714182326.GA15243@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox