linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ibm-acpi-devel@lists.sourceforge.net, linux-acpi@vger.kernel.org
Subject: Re: [GIT PULL] rename ibm-acpi driver to thinkpad-acpi
Date: Fri, 30 Mar 2007 16:03:55 -0400	[thread overview]
Message-ID: <200703301603.55424.lenb@kernel.org> (raw)
In-Reply-To: <11751443243976-git-send-email-hmh@hmh.eng.br>


+MODULE_ALIAS("ibm_acpi");
good

> 
> Len,
> 
> Please pull from: 
> git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
> branch for-upstream/acpi-test
> 
> to receive the following patches *already* in acpi-test:
>       ACPI: ibm-acpi: kill trailing whitespace
>       ACPI: ibm-acpi: rename some identifiers
>       ACPI: ibm-acpi: add header file
>       ACPI: ibm-acpi: organize code
>       ACPI: ibm-acpi: update copyright notice
>       ACPI: ibm-acpi: update documentation
>       ACPI: ibm-acpi: move driver to drivers/misc hierarchy

had these already.

> and to receive the following **new** patches:
>       ACPI: ibm-acpi: rename driver to thinkpad-acpi
>       ACPI: thinkpad-acpi: cleanup Kconfig for thinkpad-acpi
>       ACPI: thinkpad-acpi: add compatibility MODULE_ALIAS entry
>       ACPI: thinkpad-acpi: cleanup after rename
>       ACPI: thinkpad-acpi: update MAINTAINERS

applied these.


> As you can notice from the above, the branch contains the patches you have
> already pulled into acpi-test.  I don't know how well git will handle the
> merging as some *have* been rebased and whitespace-modified since you last
> pulled them (they are now exactly the same of what you have in acpi-test).
> 
> I suppose you could just drop the ones already in acpi-test and get them
> all again from the above branch, or you can get just the new ones from
> this thread using git-am.  I didn't base the branch on acpi-test, as you
> previously told me not to do that as it would make matters worse for you.
> 
> If you'd rather I prepare these branches in a different way, just tell me
> how you'd like them done.

I'm glad you're using git, it formats the patches perfectly.
But, I'll probably always apply the plain patches instead of pulling 
from your tree.  This is because i reserve the right to re-write history
of my test branch to suite my own needs, and I don't want to pull
back duplicate history from somebody that pulled acpi-test.

thanks,
-Len

  parent reply	other threads:[~2007-03-30 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29  4:58 [GIT PULL] rename ibm-acpi driver to thinkpad-acpi Henrique de Moraes Holschuh
     [not found] ` <11751443243976-git-send-email-hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-03-29  4:58   ` [PATCH 1/5] ACPI: ibm-acpi: rename " Henrique de Moraes Holschuh
2007-03-29  4:58   ` [PATCH 2/5] ACPI: thinkpad-acpi: cleanup Kconfig for thinkpad-acpi Henrique de Moraes Holschuh
2007-03-29  4:58   ` [PATCH 3/5] ACPI: thinkpad-acpi: add compatibility MODULE_ALIAS entry Henrique de Moraes Holschuh
2007-03-29  4:58   ` [PATCH 4/5] ACPI: thinkpad-acpi: cleanup after rename Henrique de Moraes Holschuh
2007-03-29  4:58   ` [PATCH 5/5] ACPI: thinkpad-acpi: update MAINTAINERS Henrique de Moraes Holschuh
2007-03-30 20:03 ` Len Brown [this message]
2007-03-30 20:06   ` [GIT PULL] rename ibm-acpi driver to thinkpad-acpi Len Brown
2007-03-31  1:03     ` Henrique de Moraes Holschuh
2007-03-31  0:56   ` Henrique de Moraes Holschuh

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=200703301603.55424.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=linux-acpi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).