From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Julia Lawall <julia@diku.dk>,
linux-pcmcia@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
walter harms <wharms@bfs.de>
Subject: Re: [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc
Date: Sat, 21 Nov 2009 16:06:54 +0000 [thread overview]
Message-ID: <20091121160654.GA11292@isilmar.linta.de> (raw)
In-Reply-To: <20091121155135.GB13956@n2100.arm.linux.org.uk>
Russell,
> Thanks for the additional info which allows me to track which patch it
> corresponds with. As an aside, it's really not nice to git pull and
> then edit the commits afterwards - that's much worse than rebasing.
> When trees are pulled, the act of merging it conveys sufficent "sign-off".
It was not a git pull and edit, as I told you in a mail sent on Nov 02:
> Thanks! I've applied the patches you sent me by mail, though, as your tree
> was based on something more recent from Linus than my tree, and I wanted to
> avoid a merge of Linus' tree into my tree.
Best,
Dominik
WARNING: multiple messages have this Message-ID (diff)
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Julia Lawall <julia@diku.dk>,
linux-pcmcia@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
walter harms <wharms@bfs.de>
Subject: Re: [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc
Date: Sat, 21 Nov 2009 17:06:54 +0100 [thread overview]
Message-ID: <20091121160654.GA11292@isilmar.linta.de> (raw)
In-Reply-To: <20091121155135.GB13956@n2100.arm.linux.org.uk>
Russell,
> Thanks for the additional info which allows me to track which patch it
> corresponds with. As an aside, it's really not nice to git pull and
> then edit the commits afterwards - that's much worse than rebasing.
> When trees are pulled, the act of merging it conveys sufficent "sign-off".
It was not a git pull and edit, as I told you in a mail sent on Nov 02:
> Thanks! I've applied the patches you sent me by mail, though, as your tree
> was based on something more recent from Linus than my tree, and I wanted to
> avoid a merge of Linus' tree into my tree.
Best,
Dominik
next prev parent reply other threads:[~2009-11-21 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 11:50 [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc Julia Lawall
2009-11-21 11:50 ` Julia Lawall
2009-11-21 12:44 ` walter harms
2009-11-21 12:44 ` walter harms
2009-11-21 15:12 ` Julia Lawall
2009-11-21 15:12 ` Julia Lawall
2009-11-21 15:16 ` Russell King - ARM Linux
2009-11-21 15:23 ` Julia Lawall
2009-11-21 15:23 ` Julia Lawall
2009-11-21 15:25 ` Dominik Brodowski
2009-11-21 15:25 ` Dominik Brodowski
2009-11-21 15:51 ` Russell King - ARM Linux
2009-11-21 15:51 ` Russell King - ARM Linux
2009-11-21 15:56 ` Julia Lawall
2009-11-21 15:56 ` Julia Lawall
2009-11-21 16:06 ` Dominik Brodowski [this message]
2009-11-21 16:06 ` Dominik Brodowski
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=20091121160654.GA11292@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=wharms@bfs.de \
/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.