From: "Ashley E Desimone" <ashley.e.desimone@intel.com>
To: devel@edk2.groups.io
Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>,
Puja Pandya <puja.pandya@intel.com>,
Erik Bjorge <erik.c.bjorge@intel.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Prince Agyeman <prince.agyeman@intel.com>
Subject: [edk2-staging/EdkRepo] [PATCH 0/2] EdkRepo: Remove duplicate function definitions
Date: Fri, 1 May 2020 13:39:44 -0700 [thread overview]
Message-ID: <20200501203946.17620-1-ashley.e.desimone@intel.com> (raw)
Remove the duplicate definition of functions in
common_repo_functions.py and update imports to use
the definitions in workspace_maintenance.py.
Signed-off-by: Ashley E Desimone <ashley.e.desimone@intel.com>
Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
Cc: Puja Pandya <puja.pandya@intel.com>
Cc: Erik Bjorge <erik.c.bjorge@intel.com>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Prince Agyeman <prince.agyeman@intel.com>
Ashley E Desimone (2):
EdkRepo: Remove duplicate definition of
generate_name_for_obsolete_backup
EdkRepo: Remove duplicate definitions of case_insensitive_single_match
and case_insensitive_equal
edkrepo/commands/clone_command.py | 3 ++-
edkrepo/commands/sync_command.py | 3 ++-
edkrepo/common/common_repo_functions.py | 35 +--------------------------------
3 files changed, 5 insertions(+), 36 deletions(-)
--
2.16.2.windows.1
next reply other threads:[~2020-05-01 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:39 Ashley E Desimone [this message]
2020-05-01 20:39 ` [edk2-staging/EdkRepo] [PATCH 1/2] EdkRepo: Remove duplicate definition of generate_name_for_obsolete_backup Ashley E Desimone
2020-05-01 20:39 ` [edk2-staging/EdkRepo] [PATCH 2/2] EdkRepo: Remove duplicate definitions of case_insensitive_single_match and case_insensitive_equal Ashley E Desimone
2020-05-05 7:41 ` [edk2-staging/EdkRepo] [PATCH 0/2] EdkRepo: Remove duplicate function definitions Nate DeSimone
2020-05-05 8:06 ` Nate DeSimone
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-list 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=20200501203946.17620-1-ashley.e.desimone@intel.com \
--to=devel@edk2.groups.io \
/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