From: Ian Jackson <ian.jackson@citrix.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
Julien Grall <julien.grall@arm.com>,
"committers@xenproject.org" <committers@xenproject.org>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream
Date: Mon, 20 May 2019 17:36:50 +0100 [thread overview]
Message-ID: <23778.55202.449293.616451@mariner.uk.xensource.com> (raw)
In-Reply-To: <2B55A18B-F04C-4249-8558-11F0A24E312C@citrix.com>
This is going in the right direction IMO.
Lars Kurth writes ("Re: [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream"):
> That makes perfect sense now. In that case, I tend to agree that "auto" is probably not needed. Would be quite happy to drop it.
It will considerably complicate things to add a way to define
seddery. Let us leave that to a future extension.
That suggests that `manual' should become `file:'.
As for delimiters
> On 17/05/2019, 01:34, "Jan Beulich" <JBeulich@suse.com> wrote:
> > I am not sure what you mean, which colons? Are you saying, the format should be
> > version: 1
> > repo: ...
>
> Yes. This would make it even more prominent that these are tags of
> some sort. But this was only a thought of mine, it's in no way meant
> to be a requirement I have.
It will make writing a parser easier if each entry is a single line
with the fields in a defined order and if we can say that a `repo:'
must precede every `file:' that mentions it.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Ian Jackson <ian.jackson@citrix.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim \(Xen.org\)" <tim@xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
Julien Grall <julien.grall@arm.com>,
"committers@xenproject.org" <committers@xenproject.org>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream
Date: Mon, 20 May 2019 17:36:50 +0100 [thread overview]
Message-ID: <23778.55202.449293.616451@mariner.uk.xensource.com> (raw)
Message-ID: <20190520163650.k-jGmf2HmYDbLElP75ZdAJUO9Q7BWRpYhytbVsjWFQM@z> (raw)
In-Reply-To: <2B55A18B-F04C-4249-8558-11F0A24E312C@citrix.com>
This is going in the right direction IMO.
Lars Kurth writes ("Re: [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream"):
> That makes perfect sense now. In that case, I tend to agree that "auto" is probably not needed. Would be quite happy to drop it.
It will considerably complicate things to add a way to define
seddery. Let us leave that to a future extension.
That suggests that `manual' should become `file:'.
As for delimiters
> On 17/05/2019, 01:34, "Jan Beulich" <JBeulich@suse.com> wrote:
> > I am not sure what you mean, which colons? Are you saying, the format should be
> > version: 1
> > repo: ...
>
> Yes. This would make it even more prominent that these are tags of
> some sort. But this was only a thought of mine, it's in no way meant
> to be a requirement I have.
It will make writing a parser easier if each entry is a single line
with the fields in a defined order and if we can say that a `repo:'
must precede every `file:' that mentions it.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-20 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 22:18 [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream Lars Kurth
2019-05-15 22:18 ` [Xen-devel] " Lars Kurth
2019-05-16 10:46 ` Jan Beulich
2019-05-16 10:46 ` [Xen-devel] " Jan Beulich
2019-05-16 15:54 ` Lars Kurth
2019-05-16 15:54 ` [Xen-devel] " Lars Kurth
2019-05-17 7:34 ` Jan Beulich
2019-05-17 7:34 ` [Xen-devel] " Jan Beulich
2019-05-20 16:05 ` Lars Kurth
2019-05-20 16:05 ` [Xen-devel] " Lars Kurth
2019-05-20 16:36 ` Ian Jackson [this message]
2019-05-20 16:36 ` Ian Jackson
2019-05-20 16:59 ` Lars Kurth
2019-05-20 16:59 ` [Xen-devel] " Lars Kurth
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=23778.55202.449293.616451@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=committers@xenproject.org \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.