From: Brian Rogers <brian@xyzw.org>
To: sreevani medhahal <sreevani.medhahal@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Regarding bluetooth-testing.git
Date: Tue, 10 Feb 2009 04:02:15 -0800 [thread overview]
Message-ID: <49916CC7.1070709@xyzw.org> (raw)
In-Reply-To: <c2a31c480902100232v56deddemc92aa954c38ef66f@mail.gmail.com>
sreevani medhahal wrote:
> hi,
>
> I would like to know if bluetooth-testing git repository has all the
> fixes for bluetooth modules, following kernel version 2.6.27 . ie., i
> want to know if i use linux kernel 2.6.27 & apply all the patches in
> bluetooth-testing git ,then will this kernel have all the fixes for
> all the known issues(only those issues whose patches were reviewed &
> acknowledged by Marcel).
>
If you applied all the patches in bluetooth-testing to your 2.6.27
kernel, you'd have a 2.6.29-rc4 kernel with some additional
Bluetooth-related patches on top of it. Branches in git still contain
all history up to the point they were branched off. Also, if you cut off
anything before the point the branch is based off (2.6.29-rc4), you'd be
excluding any fixes applied between 2.6.27 and 2.6.29-rc4. They can't
appear in the history again because you can't apply the same patch twice.
The following command will be useful to visualize changes since 2.6.27:
gitk bluetooth-testing/master ^v2.6.27 -- net/bluetooth drivers/bluetooth
(or you can pass the same parameters to 'git log')
Not everything is going to apply though, because some changes will
depend on changes in other parts of the kernel that you're skipping by
staying on 2.6.27. You'll probably have to settle for just
cherry-picking the changes you need or running a more recent kernel.
next prev parent reply other threads:[~2009-02-10 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 10:32 Regarding bluetooth-testing.git sreevani medhahal
2009-02-10 12:02 ` Brian Rogers [this message]
2009-02-10 15:35 ` Marcel Holtmann
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=49916CC7.1070709@xyzw.org \
--to=brian@xyzw.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sreevani.medhahal@gmail.com \
/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