From: Theodore Tso <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT pull] x86 fixes for 2.6.26
Date: Fri, 16 May 2008 21:57:06 -0400 [thread overview]
Message-ID: <20080517015705.GA20375@mit.edu> (raw)
In-Reply-To: <alpine.LFD.1.10.0805161544080.3020@woody.linux-foundation.org>
On Fri, May 16, 2008 at 03:47:53PM -0700, Linus Torvalds wrote:
> Do nice topic branches, where each branch has a reason for existing. The
> "x86-fixes-for-linus" branch has x86 fixes.
>
> This happens almost every time somebody starts using git properly: at that
> point the rebasing no longer hides bad habits.
Why do you consider rebasing topic branches a bad thing? It does help
keep the history much cleaner, and it means that I can test to make
sure the topic branch works well with the latest head of the
development branch.
Is there a write up of what you consider the "proper" git workflow?
- Ted
next prev parent reply other threads:[~2008-05-17 1:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 22:38 [GIT pull] x86 fixes for 2.6.26 Thomas Gleixner
2008-05-16 22:47 ` Linus Torvalds
2008-05-16 22:51 ` Linus Torvalds
2008-05-16 23:44 ` Thomas Gleixner
2008-05-17 0:03 ` Linus Torvalds
2008-05-17 0:28 ` David Miller
2008-05-17 1:38 ` Linus Torvalds
2008-05-17 19:39 ` Ingo Molnar
2008-05-17 20:00 ` Linus Torvalds
2008-05-17 21:02 ` Thomas Gleixner
2008-05-17 21:36 ` Linus Torvalds
2008-05-17 1:57 ` Theodore Tso [this message]
2008-05-17 3:19 ` Linus Torvalds
2008-05-17 14:58 ` Theodore Tso
2008-05-17 17:05 ` Linus Torvalds
2008-05-17 20:37 ` Thomas Gleixner
2008-05-17 20:26 ` Junio C Hamano
2008-05-17 22:45 ` Jesper Juhl
2008-05-18 0:35 ` Linus Torvalds
2008-05-18 2:22 ` Stephen Rothwell
2008-05-18 22:09 ` Jesper Juhl
2008-05-18 22:26 ` Linus Torvalds
2008-05-20 0:01 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2008-05-23 21:49 Thomas Gleixner
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=20080517015705.GA20375@mit.edu \
--to=tytso@mit.edu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.