linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree]
Date: Thu, 16 Sep 2021 16:27:40 +1000	[thread overview]
Message-ID: <20210916162740.3327df56@canb.auug.org.au> (raw)
In-Reply-To: <20210728071014.dkdvqmiw2lma6ooa@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

Hi Uwe,

[Sorry this took so long]

On Wed, 28 Jul 2021 09:10:14 +0200 Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
>
> I intended to take a look at the resolution that Vinod pushed in his
> tree. To find his tree and the right branch my approach in such a
> situation is usually:
> 
> 	uwe@taurus:~/gsrc/linux$ git name-rev d9e5481fca74
> 	d9e5481fca74 tags/next-20210722~22^2~2
> 
> so it was merged in tags/next-20210722~22, looking at that I see:
> 
> 	uwe@taurus:~/gsrc/linux$ git show tags/next-20210722~22
> 	commit 65da974af6a0d913cde0cf59f517322bceac24a7
> 	...
> 	    Merge remote-tracking branch 'dmaengine/next'
> 
> and then I have to lookup what dmaengine/next means in next-20210722:
> 
> 	uwe@taurus:~/gsrc/linux$ git show next-20210722 | grep dmaen
> 	...
> 	+dmaengine	git	git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git#next
> 	...
> 
> You could save me the last step if you used
> 
> 	git pull dmaengine next
> 
> instead of
> 
> 	git merge dmaengine/next
> 
> because then the commit message of tags/next-20210722~22 would be:
> 
> 	Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git
> 
> which is much more useful than
> 
> 	Merge remote-tracking branch 'dmaengine/next'
> 
> . Otherwise the result should be the same (apart from fetching the
> changes a tad later maybe).

Thanks for the feed back.

I prefer to fetch all the trees (and run my checking scripts across
them independently of the merge/build cycle.  However, I have improved
the merge commit messages (I think).  Please check out today's
linux-next.  I have decided to remove the SHA1 from the message, as you
can see that from what is merged anyway.

Let me know if this is better for you.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-09-16  6:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23  5:53 linux-next: manual merge of the dmaengine tree with the driver-core tree Stephen Rothwell
2021-07-23  9:16 ` Uwe Kleine-König
2021-07-27 13:44   ` Vinod Koul
2021-07-27 18:02     ` Dave Jiang
2021-07-28  7:10 ` Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree] Uwe Kleine-König
2021-09-16  6:27   ` Stephen Rothwell [this message]
2021-09-16  9:52     ` Uwe Kleine-König
2021-09-16 12:23       ` Stephen Rothwell

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=20210916162740.3327df56@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --subject='Re: Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree]' \
    /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

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).