linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Qian Cai <cai@lca.pw>
Cc: Linux-MM <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2020-05-05-15-28 uploaded
Date: Wed, 6 May 2020 09:59:04 -0400	[thread overview]
Message-ID: <20200506135904.GA144453@cmpxchg.org> (raw)
In-Reply-To: <518C6AC5-8938-4AD3-BE5E-0E11E2DD2929@lca.pw>

On Wed, May 06, 2020 at 08:48:27AM -0400, Qian Cai wrote:
> > On May 5, 2020, at 6:29 PM, akpm@linux-foundation.org wrote:
> > 
> > A full copy of the full kernel tree with the linux-next and mmotm patches
> > already applied is available through git within an hour of the mmotm
> > release.  Individual mmotm releases are tagged.  The master branch always
> > points to the latest release, so it's constantly rebasing.
> > 
> > 	https://github.com/hnaz/linux-mm
> > 
> > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> > contains daily snapshots of the -mm tree.  It is updated more frequently
> > than mmotm, and is untested.
> > 
> > A git copy of this tree is also available at
> > 
> > 	https://github.com/hnaz/linux-mm
> > 
> 
> Johannes, any idea why your git tree is not sync this time? The master branch is still 4-day behind.

The new mmotm tag showed up as expected:
https://github.com/hnaz/linux-mm/releases

It's just that the master branch tracked mmots only, not mmotm. It's
mostly a scripting problem around avoiding race conditions.

But this keeps causing confusion, so I changed the scripts now. Master
should now always point to the latest, whether that's mmots or mmotm.

Thanks


      reply	other threads:[~2020-05-06 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 22:29 akpm
2020-05-06  5:40 ` mmotm 2020-05-05-15-28 uploaded (objtool warning) Randy Dunlap
2020-05-08 10:38   ` Peter Zijlstra
2020-05-08 16:01     ` Josh Poimboeuf
2020-05-08 17:28     ` Randy Dunlap
2020-05-06 12:48 ` mmotm 2020-05-05-15-28 uploaded Qian Cai
2020-05-06 13:59   ` Johannes Weiner [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=20200506135904.GA144453@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=cai@lca.pw \
    --cc=linux-mm@kvack.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