ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] SPDX-License-Identifier blurbs

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Sat, 11 Nov 2017 11:43:43 +0000
My tentative plan is to convert a directory at a time and to split larger directories (e.g. epan/dissectors) into chunks. I'm not sure we should convert 3800 files in one commit:

$ git pull
$ git grep -l 'This program is free software' | wc -l
    3812

On 11/10/17 1:04 PM, Jaap Keuter wrote:
> Hi,
> 
> Maybe start off by checking other files, eg.the documentation files first.
> The dissectors are the easy targets.
> 
> Thanks,,
> Jaap
> 
>> On 10 Nov 2017, at 10:44, Darien Spencer <cusneud@xxxxxxxx
>> <mailto:cusneud@xxxxxxxx>> wrote:
>>
>> Since this patch was merged, should we start replacing (manually or
>> automaticly) the license info in other files such as dissectors?
>>  
>> *Sent:* Wednesday, November 08, 2017 at 6:09 PM
>> *From:* "Gerald Combs" <gerald@xxxxxxxxxxxxx <mailto:gerald@xxxxxxxxxxxxx>>
>> *To:* "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx
>> <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>> *Subject:* [Wireshark-dev] SPDX-License-Identifier blurbs
>> Earlier today I gave a short talk about navigating Wireshark's source
>> code. One thing I mentioned is that we have quite a bit of boilerplate at
>> the top and bottom of most files, and in the past this has confused git
>> when copying and renaming files (for me, at least).
>>
>> I've uploaded a change at https://code.wireshark.org/review/#/c/24302/
>> which starts the process of replacing the GPLv2-or-later blurb at the top
>> of various files with "SPDX-License-Identifier: GPL-2.0+". Is there any
>> reason we shouldn't go ahead with this?
> 
> 
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>