All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joshua Haberman <joshua@reverberate.org>, git@vger.kernel.org
Subject: Re: visualizing Git's Git repo
Date: Wed, 28 May 2008 01:39:16 -0700 (PDT)	[thread overview]
Message-ID: <m37ide3jtf.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0805271957430.2958@woody.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Mon, 26 May 2008, Joshua Haberman wrote:
> >
> > 2. as a project, why don't you rebase when merging long-running branches into
> > master?
> 
> For the kernel, there's been a lot of discussion about why I prefer people 
> to rebase vs merge (or often - *avoiding* merges entirely), see the kernel 
> mailing list, and search for merging. There was a thread (subject: 
> "[alsa-devel] HG -> GIT migration") about a week ago where I tried to 
> explain my opinions about about some of this.

You can read summary of this (I think) discussion at KernelTrap:
  http://kerneltrap.org/Linux/Git_Management

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      reply	other threads:[~2008-05-28  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 20:47 visualizing Git's Git repo Joshua Haberman
2008-05-26 22:59 ` Eric Hanchrow
2008-05-26 23:42   ` Joshua Haberman
2008-05-26 23:46   ` Shawn O. Pearce
2008-05-27  0:41 ` Björn Steinbrink
2008-05-27 20:36 ` Joshua Haberman
2008-05-27 23:49   ` Jeff King
2008-05-28  3:15 ` Linus Torvalds
2008-05-28  8:39   ` Jakub Narebski [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=m37ide3jtf.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=joshua@reverberate.org \
    --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.