Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Opened on 12/21/18 at 15:22:00

Closed on 04/02/20 at 20:11:17

#3668 closed defect (fixed)

Commit message in examples-v2 and libbsd didn't trigger a ticket update.

Reported by: Christian Mauderer Owned by: Amar Takhar
Priority: normal Milestone: 5.1
Component: admin Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

On 19.12.2018 I pushed a commit to the rtems-libbsd with a keyword that should have updated a ticket. But the ticket didn't pick up the commit:

Commit: ​https://git.rtems.org/rtems-libbsd/commit/?id=91566dda7f52b5eba04df159770b4797ba652f20

Ticket: ​https://devel.rtems.org/ticket/3569

The same message format worked from rtems-tools and rtems-source-builder. Did I something wrong?

Change History (2)

comment:1 Changed on 01/07/19 at 07:46:27 by Sebastian Huber

Summary: Commit message in Libbsd didn't trigger a ticket update. → Commit message in examples-v2 and libbsd didn't trigger a ticket update.

comment:2 Changed on 04/02/20 at 20:11:17 by Amar Takhar

Milestone: → 5.1
Resolution: → fixed
Status: assigned → closed

This was fixed a long time ago the issue was in the update scripts not updating multiple commits in one push only the first one was being handled.

Note: See TracTickets for help on using tickets.