From: Michael Wood <michael.g.wood@intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>,
"Lerner, David M (Wind River)" <dave.lerner@windriver.com>,
"Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [review-request] 7191 Version2 format shaid on all layers page
Date: Wed, 04 Mar 2015 15:58:10 +0000 [thread overview]
Message-ID: <54F72B92.9050105@intel.com> (raw)
In-Reply-To: <D11CAA5E.559FA%belen.barros.pena@intel.com>
Hi Dave,
Only one thing, we have renamed the branch column to "reference" because
the database confusingly splits up the vcs reference into, branch,
commit, upstream branch etc etc
We have abstracted trying to work out which to display via the function
"get_vcs_reference"
So if you switch
+ {% if o.branch|is_shaid %}
to
+ {% if o.get_vcs_reference|is_shaid %}
and you can then also remove the check to see if which kind of reference
to display
+ {% else %}
+ {{o.up_branch.name}}
It's a bit confusing so if you'd like me just to push a patch on top
then you can squash it into yours.
Michael
On 04/03/15 12:26, Barros Pena, Belen wrote:
> On 03/03/2015 22:56, "Lerner, Dave" <dave.lerner@windriver.com> wrote:
>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=lerner/layer
>> s_commitfield_7191
>>
>> 7191 - If field looks like a commit SHAID(hex and 40 digits), truncate
>> field as button label, and show full SHAID when button depressed.
> This seems to be working for me.
>
> Thanks!
>
> Belén
>
>> Dave Lerner
>>
prev parent reply other threads:[~2015-03-04 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 22:56 [review-request] 7191 Version2 format shaid on all layers page Lerner, Dave
2015-03-04 12:26 ` Barros Pena, Belen
2015-03-04 15:58 ` Michael Wood [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=54F72B92.9050105@intel.com \
--to=michael.g.wood@intel.com \
--cc=alexandru.damian@intel.com \
--cc=belen.barros.pena@intel.com \
--cc=dave.lerner@windriver.com \
--cc=toaster@yoctoproject.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.