From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Bob Copeland <me@bobcopeland.com>, arend@broadcom.com
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: obtain commit list
Date: Mon, 22 Feb 2016 14:12:36 +0100 [thread overview]
Message-ID: <56CB0944.8050205@broadcom.com> (raw)
In-Reply-To: <20160217140701.GB9315@localhost>
On 17-2-2016 15:07, Bob Copeland wrote:
> On Wed, Feb 17, 2016 at 11:40:26AM +0100, Arend Van Spriel wrote:
>> Hi Bob,
>>
>> With the old wireless testing I used to provide a list of commits that
>> were merged from wireless-testing into our internal repo. I am trying to
>> determine the strategy to produce that list with the new
>> wireless-testing using rebase stategy. Do you have a good suggestion for
>> that?
>
> Hi Arend,
>
> So I suppose it depends somewhat on how you are using the tree, whether
> you are merging w-t still or rebasing your own tree, but here's a couple
> of barely tested ideas. [Corrections welcome, I just tried a few things
> that looked "close enough", but I suppose some cases where the downstream
> trees rebase could muck up the result somewhat.]
I am actually doing a rebase of our internal tree on new w-t.
> Suppose I want to see which commits have been added between two
> wireless-testing tags, I can do, for example:
>
> git log wt-2016-02-17 ^wt-2016-02-15 -- net drivers/net/wireless | \
> git shortlog
>
> You'll see a handful of merge commits from me that don't end up in the
> upstream, but otherwise should see a reasonable set of commits that got
> merged, in this case a few iwlwifi patches.
>
> Now suppose you're rebasing your internal tree on top of w-t/master
> periodically, e.g., you have:
>
> wt-oldbase -- A -- B -- C -- D
>
> And rebase onto a new w-t tag to get (suppose A is merged upstream):
>
> wt-newbase -- B' -- C' -- D'
>
> wt-oldbase and wt-newbase actually have dated tags associated with them,
> but perhaps it is too much work to look them up and you just use
> "wireless-testing/master" in your rebase script.
Instead of doing 'git pull --rebase' I always start with 'git fetch' so
I get:
+ cdf56a8...34bbd49 master -> wl-testing/master (forced update)
which give me wt-oldbase vs wt-newbase.
> Then you could do the same thing but first get the base of the tree:
>
> wt_oldbase=$(git merge-base --fork-point wireless-testing/master D)
> wt_newbase=$(git merge-base --fork-point wireless-testing/master D')
> git log $wt_newbase ^$wt_oldbase
This time it only gave me the merge commits as there were no patches on
our drivers (I submitted ours a bit late). Still it seems this could
work for me so for that: Thanks!
Regards,
Arend
prev parent reply other threads:[~2016-02-22 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:40 obtain commit list Arend Van Spriel
2016-02-17 14:07 ` Bob Copeland
2016-02-22 13:12 ` Arend Van Spriel [this message]
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=56CB0944.8050205@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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 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.