Hi Dave,
This is the pull request that I tried to send
few days ago, but apparently I had some issue
with my mutt/smtp and it didn't go through.
Well, I don't think that there is anything critical
that cannot wait another week or -rc2
Anyway I'm sending just in case, for the record,
and to try ou
Besides drm-intel-next, sometimes it is used to re-use an
already existent tag that you just created outside
or in cases where mutt/smtp goof-up you don't want
to generate another identical tag with another date
or with "-1", "-2", etc
Suggested-by: Daniel Vetter
Cc: Daniel Vetter
Cc: Jani Nikul
I don't understand exactly why we need this special handling only
for drm-intel-next. But let's at least consolidate this into
branch_to_repo instead of spreading it around.
Cc: Jani Nikula
Cc: Daniel Vetter
Signed-off-by: Rodrigo Vivi
---
dim | 13 +
1 file changed, 5 insertions(+
By expanding the usage of new dim_pull_request_tags
we can move the drm-intel-next specific parts to
dim_pull_request_next and simplify the dim_pull_request
limiting it to only create the tags.
Cc: Daniel Vetter
Cc: Jani Nikula
Signed-off-by: Rodrigo Vivi
---
dim | 44 ++---
On Fri, Aug 24, 2018 at 8:52 AM, Jani Nikula
wrote:
> On Wed, 22 Aug 2018, Rodrigo Vivi wrote:
>> On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
>>> On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
>>>
>>> > - Sticking to fdo bugzilla and disabling gitlab issues for at least
>
