From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] fixes and support for tags
Date: Tue, 25 Jun 2019 12:26:30 +0900 [thread overview]
Message-ID: <20190625032636.10694-1-daniel.sangorrin@toshiba.co.jp> (raw)
Hello Ben,
This series contains a few fixes and support for reporting on tags.
- Re-sent patches
[cip-kernel-sec 1/6] check_git_repo: add checks to the local
I decided to remove the repository creation code from the shared
function, because it is only used by prepared_remotes.
I have adjusted the exception raised, and I use .exists() instead
of .isdir() to account for git worktrees (which I didn't know
about)
[cip-kernel-sec 2/6] prepare_remotes: helper script to prepare local
I have put the creation code here, and added remote update code
for the script to be useful.
[cip-kernel-sec 3/6] report_affected: fix code when branches are
This allows reporting on CIP branches. I have removed the
get_stable_branch function as you mentioned.
[cip-kernel-sec 4/6] report_affected: check user supplied branch
Small check to make sure the user supplied branch names actually
match the configured branches' names.
[cip-kernel-sec 5/6] report_affected: add support for reporting on
This is the new big patch, where I add support for reporting on
tags. Tags can be specified in different formats. For example:
- linux-4.4.y/v4.4.107
- v4.4.181-cip33 <-- linux-4.4.y is inferred from the tag's name
- linux-4.4.y/myproduct-v20190612 <-- product tags
[cip-kernel-sec 6/6] pep8: fix pep8-related errors such as too long
I fixed these ones because they were annoying.
Thanks,
Daniel
next reply other threads:[~2019-06-25 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 3:26 Daniel Sangorrin [this message]
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 1/6] check_git_repo: add checks to the local repository Daniel Sangorrin
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 2/6] prepare_remotes: helper script to prepare local repo Daniel Sangorrin
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 3/6] report_affected: fix code when branches are specified Daniel Sangorrin
2019-06-28 20:09 ` Ben Hutchings
2019-07-10 1:28 ` daniel.sangorrin at toshiba.co.jp
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 4/6] report_affected: check user supplied branch names Daniel Sangorrin
2019-06-28 20:12 ` Ben Hutchings
2019-07-10 1:29 ` daniel.sangorrin at toshiba.co.jp
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 5/6] report_affected: add support for reporting on tags Daniel Sangorrin
2019-06-28 20:46 ` Ben Hutchings
2019-07-10 1:36 ` daniel.sangorrin at toshiba.co.jp
2019-06-25 3:26 ` [cip-dev] [cip-kernel-sec 6/6] pep8: fix pep8-related errors such as too long lines Daniel Sangorrin
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=20190625032636.10694-1-daniel.sangorrin@toshiba.co.jp \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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 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.