Subject: osmo-pcu.git branch sysmocom/clean-ups updated. 0.2-247-ga746a50
From: [email-masked]
To: [email-masked]
Date: Wed, 4 Dec 2013 13:07:11 GMT

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "UNNAMED PROJECT".

The branch, sysmocom/clean-ups has been updated
  discards  1f5287b42e7ba453970a437cae242396066bb787 (commit)
  discards  a14e6c02bcf45060c5c7d613e2ebba8feeb55c2b (commit)
  discards  4c47ee7b7ec5ca98d2316d5738e36501bacdb48c (commit)
  discards  d4a545e17fa7d528bc6333d1f202163b95f36705 (commit)
  discards  72febb9d7492c95bf428f150fb409ad18c4fcf03 (commit)
  discards  73257c550c6ee4f6c8a435f42c33e5c1d8a19dfa (commit)
  discards  0b0b95d6fe05b8f0cdc3079fa767b3e76f70574f (commit)
  discards  6ce435e7fce91ef77734e5514d5a90978ce828a2 (commit)
  discards  1c2e3a58ad411bc9dc38715f4b85b42cd3be4a73 (commit)
  discards  41fa60059c41a3106033b08de627c12069f9c341 (commit)
       via  a746a50bf8647882ea60e8512651bb8d53be7e10 (commit)
       via  15c98f317d26bb505f4e2acc440844a52d176648 (commit)
       via  6ba04644aa41110df119cb37efcde46f38de818b (commit)
       via  50ba3c7bcdd302d9cd47895336750096b163d540 (commit)
       via  57c5214eb2ba7d76d4be72920c5c518fa2c97714 (commit)
       via  cb14362c2b8f3376468d111a12f47f01ba5a288a (commit)
       via  70b7b8e6f4053bd7ccf50766cebf6b77feb68737 (commit)
       via  b5e47d1544668eba4cea984b9a6013b07b4a3d5a (commit)
       via  bedaa03d7ba4a68adcb0d1571271dc0aeaec1a9b (commit)
       via  3c95776805e522007c9e06ac95cdf0557d9cce94 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (1f5287b42e7ba453970a437cae242396066bb787)
            \
             N -- N -- N (a746a50bf8647882ea60e8512651bb8d53be7e10)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=a746a50bf8647882ea60e8512651bb8d53be7e10

commit a746a50bf8647882ea60e8512651bb8d53be7e10
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Tue Nov 26 16:39:28 2013 +0100

    scheduling hacks..

http://cgit.osmocom.org/osmo-pcu/commit/?id=15c98f317d26bb505f4e2acc440844a52d176648

commit 15c98f317d26bb505f4e2acc440844a52d176648
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Tue Nov 26 21:01:04 2013 +0100

    rlc: Use sizeof() for the memset instead of ARRAY_SIZE
    
    In this case both will give the same result but it is better to use
    sizeof. But it is better to use the raw number of bytes instead of
    the number of elements.

http://cgit.osmocom.org/osmo-pcu/commit/?id=6ba04644aa41110df119cb37efcde46f38de818b

commit 6ba04644aa41110df119cb37efcde46f38de818b
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Tue Nov 26 16:39:47 2013 +0100

    llc: Initialize the LLC frame with garbage to detect wrong usage

http://cgit.osmocom.org/osmo-pcu/commit/?id=50ba3c7bcdd302d9cd47895336750096b163d540

commit 50ba3c7bcdd302d9cd47895336750096b163d540
Author: Daniel Willmann <[email-masked]>
Date:   Wed Nov 27 18:47:43 2013 +0100

    encoding: Change wording to match that of 3GPP TS 04.60
    
    The spec (in ch. 9.1.8.1) speaks of RECEIVED or INVALID in the RLC
    receiver, so change the wording in the log message to match.

http://cgit.osmocom.org/osmo-pcu/commit/?id=57c5214eb2ba7d76d4be72920c5c518fa2c97714

commit 57c5214eb2ba7d76d4be72920c5c518fa2c97714
Author: Daniel Willmann <[email-masked]>
Date:   Wed Nov 27 17:09:17 2013 +0100

    encoding: Use ul_window ssn()/update_rbb() methods when encoding ul ACK
    
    Use the ssn() and update_rbb() methods of gprs_rlc_ul_window when
    encoding the ACK/NACK packet in write_packet_uplink_ack()

http://cgit.osmocom.org/osmo-pcu/commit/?id=cb14362c2b8f3376468d111a12f47f01ba5a288a

commit cb14362c2b8f3376468d111a12f47f01ba5a288a
Author: Daniel Willmann <[email-masked]>
Date:   Wed Nov 27 17:56:02 2013 +0100

    tests/TypesTest: Test ssn() and update_rbb() uplink window methods in TypesTest
    
    Test that ssn and rbb are updated correctly.

http://cgit.osmocom.org/osmo-pcu/commit/?id=70b7b8e6f4053bd7ccf50766cebf6b77feb68737

commit 70b7b8e6f4053bd7ccf50766cebf6b77feb68737
Author: Daniel Willmann <[email-masked]>
Date:   Wed Nov 27 17:08:35 2013 +0100

    rlc: Manage the received block bitmap in the ul_window
    
    Added two methods to gprs_rlc_ul_window
    * ssn() returns the starting sequence number
    * update_rbb() returns an array of chars representing the state of the
      received   block bitmap. Each element is either 'I'nvalid or
      'R'eceived. The rbb is generated from v_n

-----------------------------------------------------------------------

Summary of changes:
 tests/types/TypesTest.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

hooks/post-receive
-- 
UNNAMED PROJECT