[Buildroot] [PATCH v4 3/3] minicom: add license

Giulio Benetti giulio.benetti at micronovasrl.com
Mon Aug 27 09:51:41 UTC 2018


Hello Thomas,

Il 27/08/2018 11:18, Thomas Petazzoni ha scritto:
> Hello,
> 
> On Sun, 26 Aug 2018 17:10:16 +0200, Giulio Benetti wrote:
> 
>>> diff --git a/package/minicom/minicom.hash b/package/minicom/minicom.hash
>>> index 0e94e566e7..14998edee1 100644
>>> --- a/package/minicom/minicom.hash
>>> +++ b/package/minicom/minicom.hash
>>> @@ -1,2 +1,3 @@
>>>    # Locally calculated
>>>    sha256 3bd58b594ac66545649c13ab2b728a4df0f78612eb030680d4152f7627d1f177  minicom-19ab49422f3431102c31fea01549121385113f80.tar.gz
>>> +sha256 cf80a758014eefbf068afffe3d462fc34ff4f528527524d8e100329c42094e15  COPYING
>>> \ No newline at end of file
>>
>> I've just realized this breaks make legal-info.
>> Do I need to resend patchset as v5?
> 
> Could you resend with the following order:
> 
>   1. Add hash file
>   2. Add license information
>   3. Bump to new Git version
> 
> This way, we can apply (1) and (2) to the master branch, and (3) to the
> next branch.

I've done a mistake:
on current minicom package hash exists for tarball.
on current minicom package license exists but not its hash.

Instead for new one I have to update hash file for both tarball and license.

So what I should do is:
- send a patch for adding license hash on current package(2.7-1)
- send a patch for bumping including changes for hash(tarball and license)

Right?

Thanks
Giulio


More information about the buildroot mailing list