The simplest could be
$ hg id -bi
Other(not straight) could be:
changes=$(hg outg --template '{node}\n' | egrep -v comparing\|searching | cut
-c -6); for c in $changes; do echo "[staging:$c]"; done
Thanks,
Mathi.
----- [email protected] wrote:
> Please tell how you produce those nice references to the changesets. I
> have forgotten all about it.
>
>
>
> Is it described in some text file inside repo? If not I guess it
> should…
>
>
>
> Thanks,
>
> Hans
>
>
>
>
>
>
> From: Mathi Naickan [mailto:[email protected]]
> Sent: den 7 maj 2014 11:54
> To: [email protected]
> Subject: [tickets] [opensaf:tickets] #884 LOG: opensaf saflogger
> returns EXIT_SUCCESS when saLogWriteLogAsync fails with
> SA_AIS_ERR_TRY_AGAIN
>
>
>
>
> • status : review --> fixed
> • Comment :
>
>
> [staging:2fc28b]
> [staging:00f493]
> [staging:430f08]
> [staging:69fcb9]
> [staging:a0ad3f]
> [staging:0c85ac]
>
> changeset: 5222:2fc28b657fee
> branch: opensaf-4.3.x
> parent: 5217:3e678abccbf8
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:18:33 2014 -0400
> summary: log: saflogger to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
> changeset: 5223:00f49350aae4
> branch: opensaf-4.3.x
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:19:39 2014 -0400
> summary: log: saflogtest to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
> changeset: 5224:430f08bdd695
> branch: opensaf-4.4.x
> parent: 5219:88e4c54bab4e
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:18:33 2014 -0400
> summary: log: saflogger to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
> changeset: 5225:69fcb91e5c63
> branch: opensaf-4.4.x
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:19:39 2014 -0400
> summary: log: saflogtest to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
> changeset: 5226:a0ad3fa37783
> parent: 5221:fb2540b81df4
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:18:33 2014 -0400
> summary: log: saflogger to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
> changeset: 5227:0c85acfc3c99
> tag: tip
> user: Mathivanan N.P. [email protected]
> date: Wed May 07 15:19:39 2014 -0400
> summary: log: saflogtest to return EXIT_FAILURE when
> SaLogWriteLogCallbackT fails [#884]
>
>
>
> [tickets:#884] LOG: opensaf saflogger returns EXIT_SUCCESS when
> saLogWriteLogAsync fails with SA_AIS_ERR_TRY_AGAIN
>
> Status: fixed
> Milestone: 4.3.3
> Created: Mon May 05, 2014 09:02 AM UTC by elunlen
> Last Updated: Tue May 06, 2014 11:41 AM UTC
> Owner: Mathi Naickan
>
> The function write_log_record returns errorCode if cb_error !=
> SA_AIS_OK, it should return cb_error
>
> saflogger "hej"
> Waited for 10 seconds.
> logWriteLogCallbackT FAILED: SA_AIS_ERR_TRY_AGAIN (6)
> echo $?
> 0
>
>
>
> Sent from sourceforge.net because
> [email protected] is subscribed to
> https://sourceforge.net/p/opensaf/tickets/
>
> To unsubscribe from further messages, a project admin can change
> settings at https://sourceforge.net/p/opensaf/admin/tickets/options.
> Or, if this is a mailing list, you can unsubscribe from the mailing
> list.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
