All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, Steven Rostedt <srostedt@redhat.com>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] first block round for 2.6.31
Date: Thu, 11 Jun 2009 20:52:00 +0200	[thread overview]
Message-ID: <20090611185200.GZ11363@kernel.dk> (raw)
In-Reply-To: <alpine.LFD.2.01.0906111134180.3573@localhost.localdomain>

On Thu, Jun 11 2009, Linus Torvalds wrote:
> 
> 
> On Thu, 11 Jun 2009, Jens Axboe wrote:
> > 
> > > Btw, Jens: in your tree, you've committed Tejun's changes without adding 
> > > your own sign-off. Not good!
> > 
> > That's for the patches that I pulled from his git tree. It should list
> > him as committer too.
> 
> NO!
> 
> It sounds like you have done a _major_ no-no, which is to pull from his 
> tree, and then rebase it. 
> 
> DO NOT DO THAT! NOT EVER!
> 
> If you pull from somebody elses tree, you can no longer touch the commit. 
> It absolutely has to stay the same. Otherwise we see this kind of insane 
> duplication. 
> 
> You're doing something seriously wrong here. I wrote a long rant about 
> what the rules were last release cycle, but now I can't find it. 
> Basically, if you're not the committer, you really must never EVER touch 
> it. 
> 
> [ Anybody with enough google-fu to find my rant, so I don't have to 
>   re-rant? ]

I pulled from his tree, don't think I ever rebased it. To be honest, I
rebase a lot, and I used to do that for the 'export' branches as well.
But for this cycle I have kept it clean and pulled in your tree when I
knew a conflict at arisen. More trees are now based off the block tree,
so I wanted to make sure that they were able to pull cleanly when they
wanted to. I usually also always apply the patches manually instead of
pulling it in, since I go over the patches anyway.

So I fully agree with what you are saying, if anything was rebased this
time then it was a mistake (that I don't recollect)...

-- 
Jens Axboe


  reply	other threads:[~2009-06-11 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 11:13 [GIT PULL] first block round for 2.6.31 Jens Axboe
2009-06-11 18:18 ` Linus Torvalds
2009-06-11 18:26   ` Jens Axboe
2009-06-11 18:42     ` Linus Torvalds
2009-06-11 18:52       ` Jens Axboe [this message]
2009-06-11 19:23         ` Linus Torvalds
2009-06-11 20:04           ` Jens Axboe
2009-06-11 19:58       ` Diego Calleja
2009-06-11 20:05         ` Linus Torvalds
2009-06-12  6:48   ` Borislav Petkov

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=20090611185200.GZ11363@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=srostedt@redhat.com \
    --cc=tj@kernel.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.