No, I just wanted to understand.  It will be a couple of hours work.  Tried to 
GIT clone and to add in my changes, but it didn't go well.

I will pull again over the weekend and see if my environment can compile the 
clone and then start adding things into it one at a time.

Thanks.



Herbert Falk
Solutions Architect
SISCO, INC.
6605 19 ½ Mile Rd.
Sterling Heights, MI 48314
(586) 254-0020 x-105


                                                                               
"In matters of style, swim with the current;   in matters of principle, stand 
like a rock." [Thomas Jefferson]


NOTICE: This communication may contain privileged or other confidential 
information. If you are not the intended recipient, or believe that you have  
received this communication in error, please do not print, copy, retransmit,  
disseminate, or otherwise use the information. Also,  please indicate to the 
sender that you have received this communication in error, and delete the copy 
you received. Thank you.


-----Original Message-----
From: Gerald Combs [mailto:[email protected]] 
Sent: Friday, April 04, 2014 12:09 PM
To: Developer support list for Wireshark; Herb Falk <[email protected]>
Subject: Re: [Wireshark-dev] GIT vs SVN

On 4/4/14 8:47 AM, Gerald Combs wrote:
> On 4/4/14 7:21 AM, Herb Falk <[email protected]> wrote:
>> The latest source code does not appear to be available through the 
>> use of SVN any longer?  If there is a mechanism, can somebody explain 
>> to me how to get this to work.  My current dev environment is SVN 
>> tree/managed.
> 
> We migrated to Git + Gerrit on January 28. Anonsvn.wireshark.org will 
> stay up and running for a while longer but the Wireshark SVN 
> repository is deprecated. It might be possible to create a Subversion mirror 
> (e.g.
> with SubGit or a mirror on GitHub) but I'm not sure how usable or 
> reliable that would be.

I've also configured the server to refuse SVN connections (specifically the 
OPTIONS and PROPFIND HTTP methods) for the wireshark repository under the 
assumption people might still be unaware of the migration. I'd hate to see 
someone have to merge a code base that's wildly out of sync
6 or 12 months from now.

The wireshark-win32-libs and wireshark-win64-libs repositories should still 
work. I can also un-break the wireshark repository if needed.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to