Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org, raj.khem@gmail.com
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 0/1] create-pull-request: generalize the repository URL parsing
Date: Mon, 23 May 2011 13:06:16 -0700	[thread overview]
Message-ID: <cover.1306180893.git.dvhart@linux.intel.com> (raw)

I noticed the REMOTE_REPO was not being properly parsed by the
create-pull-request script in a pull recently sent from Khem. This should
address the issue with the added benefit of treating each of pokylinux,
yoctoproject, openembedded, and github with a single regex for determining
REMOTE_REPO and public'ifying the URL. Most other repositories are also likely
covered by the new regex for generating the public URL. Specific cases are still
obviously required for generating a browsable web URL.

The following changes since commit ed8646e257ad84b017e5295b892eeb44bcef0483:

  *pull-request: add copyright, license, and descriptions (2011-05-16 15:18:20 -0700)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dvhart/git-pull
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/git-pull

Darren Hart (1):
  create-pull-request: generalize the repository URL parsing

 scripts/create-pull-request |   29 ++++++++++++-----------------
 1 files changed, 12 insertions(+), 17 deletions(-)




             reply	other threads:[~2011-05-23 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 20:06 Darren Hart [this message]
2011-05-23 20:06 ` [PATCH 1/1] create-pull-request: generalize the repository URL parsing Darren Hart
2011-05-25 17:18 ` [PATCH 0/1] " Saul Wold

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=cover.1306180893.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox