Displaying 7 results from an estimated 7 matches for "43z".
Did you mean:
43
2020 Mar 23
3
SIP/2.0 489 Bad Event in reply to a PUBLISH
..." xmlns="urn:ietf:params:xml:ns:pidf">
<tuple id="bhhmlg"> <status> <basic>open</basic> <pidfonline:online/>
</status> <contact priority="0.8">sip:john at xxx.xxx.com</contact>
<timestamp>2020-03-23T09:40:43Z</timestamp> </tuple>
</presence>
<------------->
--- (14 headers 3 lines) ---
Sending to 10.27.128.3:5060 (no NAT)
<--- Transmitting (no NAT) to 10.27.128.3:5060 --->
SIP/2.0 489 Bad Event
Via: SIP/2.0/UDP
10.27.128.3:5060;branch=z9hG4bK.GRd5yC7Wo;received=10.27.12...
2012 Jan 09
1
reposurgeon progress
...branch.
>
>ESR: In terms of content, no - not useful.
OK, crossed off my list.
>I think we have another case of some deleteall commits masking some other
>problem. From the reposurgeon Git repository, the commit "Moving
>branches/Development into trunk." (2006-02-16T13:31:43Z!clepple+nut at gmail.com)
>is a deleteall, but in our existing git-svn conversion and original SVN
>repository, that commit is a no-op (file-wise) that connects/renames the old
>branches/Development with the new trunk:
Yes, this is probably related to the fact that I'm not generating...
2012 Jan 11
1
Duplicated .gitignores solved.
...g two-parent commits right, or at least
matching what git-svn does,
# Known problems:
# 1. Merge code isn't working.
# 2. The first Eaton_SDK commit after the deleteall should have a link
# back to trunk. The commit "Moving branches/Development into trunk."
# (2006-02-16T13:31:43Z!clepple+nut at gmail.com) is a deleteall in
# reposurgeon's translation, but in the git-svn conversion and original SVN
# repository that commit is a no-op (file-wise) that connects/renames the
# old branches/Development with the new trunk. Both instances of a general
# problem: I...
2020 Mar 23
0
SIP/2.0 489 Bad Event in reply to a PUBLISH
...="urn:ietf:params:xml:ns:pidf">
> <tuple id="bhhmlg"> <status> <basic>open</basic> <pidfonline:online/>
> </status> <contact priority="0.8">sip:john at xxx.xxx.com</contact>
> <timestamp>2020-03-23T09:40:43Z</timestamp> </tuple>
> </presence>
> <------------->
> --- (14 headers 3 lines) ---
>
>
> Sending to 10.27.128.3:5060 (no NAT)
>
> <--- Transmitting (no NAT) to 10.27.128.3:5060 --->
> SIP/2.0 489 Bad Event
> Via: SIP/2.0/UDP
> 10.27.12...
2006 Mar 16
0
(no subject)
...m:;;420 N 5th St. Suite #865;Minneapolis;Mn;55401
email;TYPE=internet:linde@imageman.com
tel;TYPE=work:612-746-5706
tel;TYPE=fax:612-746-5781
tel;TYPE=cell:763-438-1781
x-mozilla-html:TRUE
url:http://www.imageman.com
X-EVOLUTION-FILE-AS:Linde\, Larry
UID:pas-id-440C50B700000001
REV:2006-03-06T15:09:43Z
END:VCARD
2012 Jan 25
4
serializable_hash and serializable_add_includes
I''m trying to write a helper method similar to attr_accessible but
instead it will be used to whitelist which attributes are available for
serialization (attr_serializable). My first attempt at this was to
override serialized_hash and modify the :only option to include nothing
but serializable attributes. I''m facing a problem when nested models
are ''included''
2012 Jan 07
3
Mixed-commit problem solved
Well, that wasn't as nasty as I feared it would be. Turns out that in
the general case it's possible to partition a mixed-branch revision
into branch cliques and generate multiple import-stream commits, one
for each affected branch.
We lose only if the split commit is the source of a later directory
copy; I have a check for that that says, basically, "if you see this
fatal error,