git push
ssh://@test.code.wireshark.org:29418/wireshark-review-sandbox
HEAD:refs/for/master%topic=reload-patchsets
This way you can click on the topic, and see all the related patchsets.
To prevent name clashing, some sort of naming scheme for the topics should be
created (/ ?)
- --
Marc Peti
e merge in master.
Personally I like to start my day of work with a pull and a round of rebase in
all my topic branches, as I keep forgetting to rebase my branches when I had
to fix something following a review.
>
> Thanks, Evan
>
> On 2013-09-18, at 8:52 PM, Marc Petit-Huguenin
&g
the branch will not be
deleted if it was not completely merged):
git checkout master
git branch -d first-patchset-master
Enjoy!
- --
Marc Petit-Huguenin
Email: m...@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-BEG
ypassed review a couple of times by doing a default
> push, but that might just be me.
A good way to fix that is to run the following command, so a "git push" will
always push in the right destination:
git config --add remote.origin.push HEAD:refs/for/master
- --
Marc Petit-Hugueni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/28/2013 07:57 AM, Marc Petit-Huguenin wrote:
> On 06/28/2013 07:21 AM, Jeff Morriss wrote:
>> On 06/22/13 06:47, Bálint Réczey wrote:
>>> Hi All,
>>>
>>> 2013/6/21 Marc Petit-Huguenin :
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/28/2013 07:21 AM, Jeff Morriss wrote:
> On 06/22/13 06:47, Bálint Réczey wrote:
>> Hi All,
>>
>> 2013/6/21 Marc Petit-Huguenin :
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/22/2013 09:43 AM, Bálint Réczey wrote:
> Hi Marc,
>
> 2013/6/22 Marc Petit-Huguenin :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 06/22/2013 03:47 AM, Bálint Réczey wrote:
>>> Hi All,
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/22/2013 03:47 AM, Bálint Réczey wrote:
> Hi All,
>
> 2013/6/21 Marc Petit-Huguenin :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 06/20/2013 04:52 PM, Guy Harris wrote:
>>>
>>> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/20/2013 02:58 PM, Marc Petit-Huguenin wrote:
> On 06/20/2013 02:17 PM, Gerald Combs wrote:
>> The following subjects came up during developer discussions at Sharkfest
>> this year:
>
>
> [...]
>
>> Git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/20/2013 04:52 PM, Guy Harris wrote:
>
> On Jun 20, 2013, at 2:58 PM, Marc Petit-Huguenin
> wrote:
>
>> On 06/20/2013 02:17 PM, Gerald Combs wrote:
>>
>>> Advantates: - I'm not sure that an in-ho
ry about / manage.
>
> Disadvantages: - This would mean transitioning to an different workflow.
>
- --
Marc Petit-Huguenin
Email: m...@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-BEGIN PGP SIGNATURE-
Versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/02/2012 12:03 PM, Guy Harris wrote:
>
> On Nov 2, 2012, at 6:47 AM, Marc Petit-Huguenin
> wrote:
>
>> But I think that this kind of redundancy, that can only create
>> interoperability issues or security vulnerabil
wly designed file format. Is there a process existing to evolve this
format? The spec has been written with IETF tools, but I cannot find a
submission for it. I can help navigate the IETF process if there is an
interest in pushing this spec as a standard. I think that this is typically
the kin
- --
Marc Petit-Huguenin
Email: m...@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQktt7AAoJECnERZXWan7E/K0P/j/HE/5vkOQAyB2vLi83qSvw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It seems that the git repository has not been synchronized since November 25th,
stopping at svn commit #40003.
- --
Marc Petit-Huguenin
Personal email: m...@petit-huguenin.org
Professional email: petit...@acm.org
Blog: http://blog.marc.petit
correct way to have a patch considered for inclusion? (We
followed
http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html#ChSrcSend)
Thanks.
- --
Marc Petit-Huguenin
Personal email: m...@petit-huguenin.org
Professional email: petit...@acm.org
Blog: http://blog.marc.petit-huguenin.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/2011 11:14 AM, Guy Harris wrote:
>
> On Aug 17, 2011, at 10:46 AM, Marc Petit-Huguenin wrote:
>
>> I think it would be great to have a standard XML parser available in
>> Wireshark - for my dissector, it would be to p
contribute XML files to Wireshark.
I think it would be great to have a standard XML parser available in Wireshark -
for my dissector, it would be to parse the XML document that is embedded in the
ConfigUpdate RELOAD message.
I would suggest to look at the VTD-XML[1] parser, which is extremely fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I moved back to gcc-4.6 and the new Debian version 4.6.1-5 is now building
Wireshark fine.
On 08/02/2011 09:24 AM, Bill Meier wrote:
> On 8/2/2011 11:19 AM, Marc Petit-Huguenin wrote:
>>
>> I had the same exact problem when my Debian s
t use in
> this
> function)
I had the same exact problem when my Debian sid distribution updated the gcc 4.6
compiler. I use 4.5 instead, and everything works.
- --
Marc Petit-Huguenin
Personal email: m...@petit-huguenin.org
Professional email: petit...@acm.org
Blog: http://blog.marc.pet
Martin Kaiser wrote:
>Hello Guy, all,
>
>thanks for your feedback.
>
>Thus wrote Guy Harris (g...@alum.mit.edu):
>
>> > In order to populate the nstime_t, I set the seconds directly, e.g.
>
>> > nstime_t my_time;
>> > my_time.secs = tvb_get_guint8(tvb, offset);
>
>> > Is this portable enough wi
the packets to
dissect.
So my question is: What is the best way to do this?
Thanks.
- --
Marc Petit-Huguenin
Personal email: m...@petit-huguenin.org
Professional email: petit...@acm.org
Blog: http://blog.marc.petit-huguenin.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Morriss wrote:
> Marc Petit-Huguenin wrote:
>> I need an advice for a special case I'll have to implement. The regular
>> packets to be dissected does not contains enough information to select
>> the right diss
use the same
dissector? Obviously, if the packets 1 and 2 are missing, then the
dissector cannot be selected. Packets can be carried by UDP or TCP (or
SCTP or DCCP...)
The name of an existing dissector implementing something similar would
also be useful.
Thanks.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Morriss wrote:
> Marc Petit-Huguenin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> Please find attached a new version of the patch.
>
> Checked in (rev 22383), thanks!
>
> B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Morriss wrote:
> Marc Petit-Huguenin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>>
>> This is an update to the STUN2 dissector using the last draft,
>> draft-ietf-behave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Morriss wrote:
> Marc Petit-Huguenin wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi,
>>
>> This is an update to the STUN2 dissector using the last draft,
>> draft-ietf-behav
rder of attributes in the dissector code.
* The message length is now displayed in decimal.
I will update the Wiki page accordingly.
- --
Marc Petit-Huguenin [ ]
Home: [EMAIL PROTECTED] [RFC1855-compliant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Fisher wrote:
> On Wed, Dec 13, 2006 at 02:23:54PM -0800, Stephen Fisher wrote:
>> On Wed, Dec 06, 2006 at 08:03:56AM -0800, Marc Petit-Huguenin wrote:
>>
>>> I initially tried to implement the new STUN (STUNv2) in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Morriss wrote:
>
> Marc Petit-Huguenin wrote:
>> Hi,
>>
>> This is a new dissector for STUN v2, that is currently in WGLC at the IETF.
>>
>> The packet-stun.c file must be copied into packet-stun2.c before
.
- --
Marc Petit-Huguenin [ ]
Home: [EMAIL PROTECTED] [ RFC1855-compliant space for rent]
Work: [EMAIL PROTECTED][ ]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla
31 matches
Mail list logo
