From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [git pull] x86: declaration fixes - ver2
Date: Wed, 23 Jul 2008 09:32:33 +0200 [thread overview]
Message-ID: <20080723073233.GA21172@elte.hu> (raw)
In-Reply-To: <1216786052.2602.2.camel@jaswinder.satnam>
* Jaswinder Singh <jaswinder@infradead.org> wrote:
> Hello Ingo,
>
> Here are updated patches for x86-tip.
>
> The following changes since commit a099a9b18ab434594bb01ed920e8c58574203fa9:
> Ingo Molnar (1):
> Merge branch 'out-of-tree'
looks good, but could you please switch over the changes to be based on
the "upstream" topic branch of your patches, i.e. to tip/x86/prototypes?
You can do it the following way:
git checkout master
git merge tip/master # get latest
git checkout -b x86/prototypes-for-tip # new pull branch
git rebase --onto tip/x86/prototypes tip/master # switch
In theory this should run just fine without any conflicts or manual
intervention needed.
If that rebase command ran fine, double-check the end result by looking
at the output of:
git log tip/x86/prototypes..x86/prototypes-for-tip
... then resend the pull request for the x86/prototypes branch you have,
by doing something like:
git-request-pull tip/x86/prototypes git://git.infradead.org/users/jaswinder/linux-2.6-tip.git x86/prototypes-for-tip
The reason for not basing your branch on tip/master is that we want to
keep x86/protypes topic a "pure" topic that is mergable without waiting
for other topics - without mixing it with all other topics that are
integrated into tip/master.
And note that x86/prototypes-for-tip is a by-line branch that you should
not touch after sending the pull request (so that what i pull matches up
to the summary in the email you send) - you can still evolve your master
branch with other work, create other branches, etc.
Let me know if there's any Git hickup.
Thanks,
Ingo
next prev parent reply other threads:[~2008-07-23 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 4:07 [git pull] x86: declaration fixes - ver2 Jaswinder Singh
2008-07-23 7:32 ` Ingo Molnar [this message]
2008-07-23 12:34 ` Jaswinder Singh
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=20080723073233.GA21172@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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