public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Updated ext4/jbd2 patches based on 2.6.19-rc1
Date: Fri, 6 Oct 2006 09:11:48 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610060908380.3952@g5.osdl.org> (raw)
In-Reply-To: <1160139032.8658.17.camel@kleikamp.austin.ibm.com>



On Fri, 6 Oct 2006, Dave Kleikamp wrote:
> On Thu, 2006-10-05 at 16:25 -0700, Linus Torvalds wrote:
> 
> We haven't been using git to manage ext4 so far, although in hindsight
> it probably would have made things easier.  I'm assuming that you're
> just suggesting this for educational purposes and that git will handle
> the patches that Andrew picked up into -mm just fine.

Well, also that even if you're not using git, what any random person can 
do is to actually just import the current state into git, and do the 
simple "git diff -C" thing to get the nicer diff.

One of the advantages about git is that "intent" doesn't matter. Git only 
tracks cold, hard data. So if you copied a file, git doesn't care one whit 
whether you _tell_ it that you copied it or not: it will purely look at 
the end result, and say "you copied it" if the file looks the same.

> I could re-generate the patches that do the copies from git, but I don't
> believe it will be that beneficial at this point.

The only advantage (but I'd argue that it's a real one, and very possibly 
worth it) is that when this gets sent to me (or anybody else) by email, it 
can be sent in a format that is actually readable, instead of sending it 
as a huge patch that doesn't actually talk about what it does..

		Linus

  reply	other threads:[~2006-10-06 16:11 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 18:23 Updated ext4/jbd2 patches based on 2.6.19-rc1 Dave Kleikamp
2006-10-05 20:19 ` Andrew Morton
2006-10-05 23:25   ` Linus Torvalds
2006-10-06 12:50     ` Dave Kleikamp
2006-10-06 16:11       ` Linus Torvalds [this message]
2006-10-05 21:59 ` Andrew Morton
2006-10-06  0:39 ` Andrew Morton
2006-10-10  6:29   ` Andrew Morton
2006-10-10  7:54     ` Suparna Bhattacharya
2006-10-10  8:14       ` Andrew Morton
2006-10-10 20:02         ` [RFC] [PATCH] Documentation/filesystems/ext4.txt Dave Kleikamp
2006-10-10 20:56           ` Andrew Morton
2006-10-11 17:03           ` Andreas Dilger
2006-10-12 14:18           ` Valerie Clement
2006-10-06  3:55 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06  3:58   ` Andrew Morton
2006-10-06 10:34     ` Alex Tomas
2006-10-06  4:54   ` Randy Dunlap
2006-10-06  5:05     ` Andrew Morton
2006-10-06  5:53     ` Andreas Dilger
2006-10-06  6:04       ` Andrew Morton
2006-10-06  6:41         ` Andreas Dilger
2006-10-06  6:50           ` Andrew Morton
2006-10-06 10:31             ` Alex Tomas
2006-10-06 13:57               ` Andrew Morton
2006-10-07 20:09                 ` alex
2006-10-06  6:52           ` Suparna Bhattacharya
2006-10-06 12:21   ` Theodore Tso
2006-10-06 21:10     ` [PATCH] Get rid of extents mount option Dave Kleikamp
2006-10-06 21:21       ` [PATCH] Get rid of extents mount option - try 2 Dave Kleikamp
2006-10-06 22:32         ` Andrew Morton
2006-10-06 23:20           ` Dave Kleikamp
2006-10-07  4:14             ` Theodore Tso
2006-10-07 15:53               ` Dave Kleikamp
2006-10-07 17:20                 ` Theodore Tso
2006-10-07 19:45                   ` Alex Tomas
2006-10-07 19:57                   ` Andrew Morton
2006-10-10 18:48                   ` Dave Kleikamp
2006-10-10 21:07                     ` Theodore Tso
2006-10-10 21:18                       ` Andrew Morton
2006-10-11 17:16         ` Andreas Dilger
2006-10-06  4:31 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06  5:58   ` Andreas Dilger
2006-10-06  6:10     ` Andrew Morton
2006-10-06  6:48       ` Andreas Dilger

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=Pine.LNX.4.64.0610060908380.3952@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shaggy@austin.ibm.com \
    /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