All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] timezone:upgrade 2019b -> 2019c
Date: Thu, 12 Sep 2019 17:28:24 +0300	[thread overview]
Message-ID: <20190912142824.GB5021@localhost> (raw)
In-Reply-To: <e91aab69-d7ab-dd80-1671-72e21e85711b@gmail.com>

On Thu, Sep 12, 2019 at 07:10:08AM -0700, akuster808 wrote:
> 
> 
> On 9/11/19 11:52 PM, Zang Ruochen wrote:
> > -tzdata : upgrade from 2019b to 2019c.
> >
> > -tzcode-native : upgrade from 2019b to 2019c.
> >
> > -tzdata.bb and tzcode-native.bb require timezone.inc.
> 
> Not exactly what I had in mind.  When there is a TZ update they send out
> what changed any why.  It looks like this"
>...

IMHO that would be far too long for a commit message,
and changelogs of this size would make the git history
unreadable if everyone would start pasting huge upstream
changelogs in their commits.

cu
Adrian

BTW: How is the legal handling of the metadata, when such lengthy
     3rd party texts copyrighted by various people under various 
     licences are distributed as part of the git metadata?

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-09-12 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12  6:52 [PATCHv2] timezone:upgrade 2019b -> 2019c Zang Ruochen
2019-09-12 14:10 ` akuster808
2019-09-12 14:28   ` Adrian Bunk [this message]
2019-09-12 17:30     ` akuster808
2019-09-13 15:03       ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190912142824.GB5021@localhost \
    --to=bunk@stusta.de \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.