All of lore.kernel.org
 help / color / mirror / Atom feed
From: suratiamol at gmail.com (Amol Surati)
Subject: [Linux-kernel-mentees] git: Behaviour of the stable-rc repo
Date: Sat, 6 Jul 2019 12:28:07 +0530	[thread overview]
Message-ID: <20190706065655.GA10163@arch> (raw)

Hi,

Since yesterday, the stable-rc branch 'linux-5.1.y' has received new
commits.

There were 7 code-change-commits + 1 version-change-commit, which were
based on the released 5.1.16. Now, when the branch has been refreshed
(twice afaics) with new commits, those 8 previous commits have been assigned
new identities (still based on 5.1.16).

It seems that there are 3 copies of those 8 commits.
For e.g., the version-change-commit has these IDs -

57f5b343cdf9593b22d79f5261f30243c07d6515,
925bedf91c6bb194cb6b23a553cb8469f3a2007f, and
2b5fd394355ac0b2cc9572232727cb2bce7c15a7

with 2b5... being the most recent ID (and the HEAD iinm).

Could you help me understand how these copies are created, and why?

Also, why do we want to commit the version update, if more commits are
expected to arrive on top of it?

Thanks,
amol

WARNING: multiple messages have this Message-ID (diff)
From: suratiamol@gmail.com (Amol Surati)
Subject: [Linux-kernel-mentees] git: Behaviour of the stable-rc repo
Date: Sat, 6 Jul 2019 12:28:07 +0530	[thread overview]
Message-ID: <20190706065655.GA10163@arch> (raw)
Message-ID: <20190706065807.A0uQkJwn0Jkn3DkfdkZtmqq6weUdgPZ5RQpOG2GgBgU@z> (raw)

Hi,

Since yesterday, the stable-rc branch 'linux-5.1.y' has received new
commits.

There were 7 code-change-commits + 1 version-change-commit, which were
based on the released 5.1.16. Now, when the branch has been refreshed
(twice afaics) with new commits, those 8 previous commits have been assigned
new identities (still based on 5.1.16).

It seems that there are 3 copies of those 8 commits.
For e.g., the version-change-commit has these IDs -

57f5b343cdf9593b22d79f5261f30243c07d6515,
925bedf91c6bb194cb6b23a553cb8469f3a2007f, and
2b5fd394355ac0b2cc9572232727cb2bce7c15a7

with 2b5... being the most recent ID (and the HEAD iinm).

Could you help me understand how these copies are created, and why?

Also, why do we want to commit the version update, if more commits are
expected to arrive on top of it?

Thanks,
amol

             reply	other threads:[~2019-07-06  6:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06  6:58 suratiamol [this message]
2019-07-06  6:58 ` [Linux-kernel-mentees] git: Behaviour of the stable-rc repo Amol Surati
2019-07-06  8:19 ` gregkh
2019-07-06  8:19   ` Greg KH
2019-07-06  9:19   ` suratiamol
2019-07-06  9:19     ` Amol Surati
2019-07-06  9:41     ` gregkh
2019-07-06  9:41       ` Greg KH
2019-07-06  9:45       ` gregkh
2019-07-06  9:45         ` Greg KH
2019-07-06 15:08         ` suratiamol
2019-07-06 15:08           ` Amol Surati
2019-07-06 15:06       ` suratiamol
2019-07-06 15:06         ` Amol Surati
2019-07-13  8:32       ` sheriffesseson
2019-07-13  8:32         ` Sheriff Esseson
2019-07-13 14:37         ` gregkh
2019-07-13 14:37           ` Greg KH
2019-07-13 16:07           ` sheriffesseson
2019-07-13 16:07             ` Sheriff Esseson
     [not found]           ` <20190713160035.GA11449@localhost>
     [not found]             ` <20190713160707.GA18148@kroah.com>
2019-07-13 19:59               ` sheriffesseson
2019-07-13 19:59                 ` Sheriff Esseson

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=20190706065655.GA10163@arch \
    --to=unknown@example.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.