Russ Allbery writes:
> The killer features of YAML for the purposes of the copyright format are
> the > and | symbols after a key, which let you write paragraphs of text
> afterwards with normal structural indentation and full editor support
> for wrapping and the like, and you can choose whether
Guillem Jover writes:
> I think Disclaimer and Comment do not seem as problematic because they
> tend to contain descriptive prose. For Source it's true that it's weird
> as it seems to indeed want to have two different semantics depending on
> the content, and considering the current deb822 form
Wouter Verhelst writes:
> On Sun, Sep 18, 2022 at 06:01:38PM -0700, Russ Allbery wrote:
>> Yes, we should distinguish between formatted text with synopsis and
>> formatted text without synopsis more clearly. Or, you know, just
>> propose a new YAML format which would make it trivial to clean up
On Sun, Sep 18, 2022 at 06:01:38PM -0700, Russ Allbery wrote:
> Guillem Jover writes:
>
> > Oh! I've completely missed this all this time, I think because that
> > feels very weird given that it has no synopsis and the text is added
> > already on the first line on the spec. :/
>
> Other formatt
On Sun, 2022-09-18 at 18:01:38 -0700, Russ Allbery wrote:
> Guillem Jover writes:
>
> > Oh! I've completely missed this all this time, I think because that
> > feels very weird given that it has no synopsis and the text is added
> > already on the first line on the spec. :/
>
> Other formatted f
Guillem Jover writes:
> No problem. Then in that case I guess I'll try to prepare/commit such
> revert patches for the tooling during this week or so.
For whatever it's worth, I'm not sure that I would bother, even though I
share with you the general desire to be correct about things like this.
On Sun, 2022-09-18 at 18:04:00 -0700, Russ Allbery wrote:
> Guillem Jover writes:
> > BTW, just to make this clear, if this feels like it might not be decided
> > quickly on the Debian policy side, then I'll prepare/commit changes to
> > revert this behavior from tooling that I've previously intro
Guillem Jover writes:
> On Sun, 2022-09-18 at 22:56:16 +0200, Guillem Jover wrote:
>> On Sun, 2022-09-18 at 10:58:20 -0700, Russ Allbery wrote:
>>> Russ Allbery writes:
I would happily apply a version of 0002 that only changes Files and
leaves Copyright alone.
>> I can split that up,
Guillem Jover writes:
> Oh! I've completely missed this all this time, I think because that
> feels very weird given that it has no synopsis and the text is added
> already on the first line on the spec. :/
Other formatted fields with the same semantics are Source, Disclaimer, and
Comment. I do
Hi!
On Sun, 2022-09-18 at 22:56:16 +0200, Guillem Jover wrote:
> On Sun, 2022-09-18 at 10:58:20 -0700, Russ Allbery wrote:
> > Russ Allbery writes:
> > > I would happily apply a version of 0002 that only changes Files and
> > > leaves Copyright alone.
>
> I can split that up, for an incremental
Hi!
On Sun, 2022-09-18 at 10:42:28 -0700, Russ Allbery wrote:
> Guillem Jover writes:
>
> > These are the set of changes I keep doing to the debian/copyright files
> > I end up touching. While some could be characterized as a subjective
> > style issue, I've tried to give as close as possibly ob
Russ Allbery writes:
> I would happily apply a version of 0002 that only changes Files and
> leaves Copyright alone.
Or, perhaps even better, one that changes Copyright the way that you did,
but just adds an extra space. I think that's the simplest compromise
between what you're trying to accom
Guillem Jover writes:
> These are the set of changes I keep doing to the debian/copyright files
> I end up touching. While some could be characterized as a subjective
> style issue, I've tried to give as close as possibly objective :)
> rationale for every and each of the changes in the commit me
Package: debian-policy
Version: 4.6.1.1
Severity: wishlist
Tags: patch
Hi!
These are the set of changes I keep doing to the debian/copyright
files I end up touching. While some could be characterized as a
subjective style issue, I've tried to give as close as possibly
objective :) rationale for e
14 matches
Mail list logo
