From: shiraz.hashim@st.com (Shiraz Hashim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: spear-soc DT support for 3.5
Date: Wed, 11 Apr 2012 14:34:34 +0530 [thread overview]
Message-ID: <20120411090434.GX1781@localhost.localdomain> (raw)
In-Reply-To: <CACRpkdaU8yVAnsvL3JBh-XZv0pQ0jtdDOz97nF2v7LbQoYRz_g@mail.gmail.com>
On Wed, Apr 11, 2012 at 04:54:01PM +0800, Linus Walleij wrote:
> On Wed, Apr 11, 2012 at 10:47 AM, Viresh Kumar <viresh.kumar@st.com> wrote:
> > On 4/11/2012 2:13 PM, Linus Walleij wrote:
> >> Yeah you can send this pull request and then Arnd or Olof will put it
> >> on some topic branch like "topic-spear" and then you base your
> >> further work on top of that and then send a new pull request to be
> >> merged into that same branch, with the pinctrl stuff. And include the
> >> ACK:s directly in the patches (git rebase -i is your friend...)
> >
> > git rebase -i is an old friend, but it seem i don't know him completely :(
> > How does it help in adding Acked-by automatically? Is there anything more
> > than marking all of them as "rework" and add these Acks manually?
>
> Not that I'm aware of ... That's how I do it atleast.
In your 'git party' I remember, someone mentioning about 'git
filter-branch' which can help on this. Perhaps we need to go through
the help pages.
--
regards
Shiraz
next prev parent reply other threads:[~2012-04-11 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 5:42 [GIT PULL] ARM: spear-soc DT support for 3.5 Viresh Kumar
[not found] ` <CAOh2x=n8GO-vzFgDEdeyUVdGiOE_-BxgpC5+LbKRMtvgnoSxHQ@mail.gmail.com>
2012-04-10 8:42 ` Linus Walleij
2012-04-10 9:18 ` Viresh Kumar
2012-04-11 8:17 ` Linus Walleij
2012-04-11 8:24 ` Viresh Kumar
2012-04-11 8:43 ` Linus Walleij
2012-04-11 8:47 ` Viresh Kumar
2012-04-11 8:54 ` Linus Walleij
2012-04-11 9:04 ` Shiraz Hashim [this message]
2012-04-11 8:16 ` Linus Walleij
2012-04-11 8:23 ` Viresh Kumar
2012-04-11 17:30 ` Arnd Bergmann
2012-04-12 6:49 ` Viresh Kumar
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=20120411090434.GX1781@localhost.localdomain \
--to=shiraz.hashim@st.com \
--cc=linux-arm-kernel@lists.infradead.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.