[Paul Offord <Paul.Offord@xxxxxxxxxxxx>]

Thanks Pascal, That’s very useful.

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Pascal Quantin
Sent: 17 January 2017 14:46
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Building against 2.2.3 after git clone

 

Hi Paul

 

2017-01-17 15:43 GMT+01:00 Paul Offord <Paul.Offord@xxxxxxxxxxxx>:

Hi,

 

At last I have managed to create my WS dev VM.  I installed the WS source with:

 

 git clone https://code.wireshark.org/review/wireshark

 

I want to build a plugin against the 2.2.3 release.  Do I have to pull a 2.2.3 repository or can I just do a branch switch or something with my current local repository?

 

You can switch to the branch used by Wireshark 2.2.X releases with 'git checkout master-2.2'. If you specifically want 2.2.3 source code, use 'git checkout wireshark-2.2.3'.

Regards,

Pascal.

______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________