Le Tue, Sep 10, 2013 at 11:23:55AM +0200, Guillem Jover a écrit :
On Sat, 2013-08-31 at 18:17:29 +0900, Charles Plessy wrote:
In any case, we need one more Developer to support this patch before
applying to
the Policy. Once we have this extra assessment for consensus, I will apply
it
Hi!
On Sat, 2013-08-31 at 18:17:29 +0900, Charles Plessy wrote:
In any case, we need one more Developer to support this patch before applying
to
the Policy. Once we have this extra assessment for consensus, I will apply it
unless there are clear objections. Guillem, please raise your hand
Charles Plessy wrote:
Le Sat, Aug 31, 2013 at 06:17:29PM +0900, Charles Plessy a écrit :
In any case, we need one more Developer to support this patch before
applying to
the Policy. Once we have this extra assessment for consensus, I will apply
it
unless there are clear
On 8 September 2013 10:12, Charles Plessy ple...@debian.org wrote:
Le Sat, Aug 31, 2013 at 06:17:29PM +0900, Charles Plessy a écrit :
In any case, we need one more Developer to support this patch before
applying to
the Policy. Once we have this extra assessment for consensus, I will apply
tag 720507 pending
thanks
Le Mon, Sep 09, 2013 at 11:46:11AM -0400, Joey Hess a écrit :
I support this proposal and this particular implementation of it.
Le Mon, Sep 09, 2013 at 04:49:01PM +0100, Dmitrijs Ledkovs a écrit :
I support this proposal and this particular implementation of it.
Le Sat, Aug 31, 2013 at 06:17:29PM +0900, Charles Plessy a écrit :
In any case, we need one more Developer to support this patch before applying
to
the Policy. Once we have this extra assessment for consensus, I will apply it
unless there are clear objections.
Ping ?
--
Charles Plessy
tag 720507 patch
thanks
Le Thu, Aug 29, 2013 at 02:00:40AM +0100, Ian Jackson a écrit :
Charles Plessy writes (Re: Bug#720507: .dsc field for dgit [and 1 more
messages]):
Here is a simplified patch, written under the assumption of Dgit for the
name.
Thanks.
I made the following
Charles Plessy writes (Re: Bug#720507: .dsc field for dgit [and 1 more
messages]):
Here is a simplified patch, written under the assumption of Dgit for the
name.
Thanks.
I made the following changes:
[stuff]
Right. That all sounds excellent thanks.
(However, did you edit the diff by hand
Guillem Jover writes (Re: Bug#720507: .dsc field for dgit):
It seems premature to me to document this in policy while as you
recognize elsewhere this is for now still just an experiment. In a way
I guess I also fail to see the need to document it at all in policy
given that it's a tool
Hi,
On Fri, 23 Aug 2013, Ian Jackson wrote:
I think this is starting to convince me that this means I should be
using a different kind of field name. This isn't really suitable. In
particular, it shouldn't interact with any deliberate setting of Vcs-*
by the maintainer.
Yes, Dgit-Commit or
Charles Plessy writes (Re: Bug#720507: .dsc field for dgit):
thank you for your patch and for your work on dgit. In light of the
discussion about how our infrastructure handles this field, I would
like to wait for further testing and adoption before adding it to
the Policy. Please do
Ian Jackson ijack...@chiark.greenend.org.uk writes:
Is just Dgit too short ?
Works for me.
Bdale
pgpOMRw8XMUci.pgp
Description: PGP signature
Hi!
On Thu, 2013-08-22 at 18:48:02 +0100, Ian Jackson wrote:
Package: debian-policy
Version: 3.9.4.0
I have been working on a new tool for integration between the Debian
archive and git. The best available description is probably its
manpage:
Thanks Ian and everybody for your comments.
Here is a simplified patch, written under the assumption of Dgit for the
name.
I made the following changes:
- Removed mention that this field is only in Debian source control files and
must not be present in source package control files: it is
Package: debian-policy
Version: 3.9.4.0
I have been working on a new tool for integration between the Debian
archive and git. The best available description is probably its
manpage:
http://www.chiark.greenend.org.uk/~ijackson/2013/dgit.html
dgit uses a new field in .dsc files, which I have
On 22 August 2013 18:48, Ian Jackson ijack...@chiark.greenend.org.uk wrote:
Package: debian-policy
Version: 3.9.4.0
I have been working on a new tool for integration between the Debian
archive and git. The best available description is probably its
manpage:
Dmitrijs Ledkovs writes (Re: Bug#720507: .dsc field for dgit):
Using this field, seems to miss-render on Debian PTS.
See: http://packages.qa.debian.org/d/dgit.html
Click on the link next to VCS: it goes nowhere =)
Hmm. Would it be better to pick a different name ? It's not too late
- I
On 22 August 2013 20:53, Ian Jackson ijack...@chiark.greenend.org.uk wrote:
Dmitrijs Ledkovs writes (Re: Bug#720507: .dsc field for dgit):
Using this field, seems to miss-render on Debian PTS.
See: http://packages.qa.debian.org/d/dgit.html
Click on the link next to VCS: it goes nowhere
Dmitrijs Ledkovs writes (Re: Bug#720507: .dsc field for dgit):
No idea. I guess Debian PTS blindly copies displays any Vcs-*:
fields as the URL.
It would then work if that field would be a valid url e.g.:
http://anonscm.debian.org/gitweb/?p=dgit-repos/dgit.git;a=commit;h
user debian-pol...@packages.debian.org
severity 720507 wishlist
usertags 720507 normative issue
thanks
Le Thu, Aug 22, 2013 at 06:48:02PM +0100, Ian Jackson a écrit :
I have been working on a new tool for integration between the Debian
archive and git. The best available description is
Charles Plessy wrote:
About the specification of the commit hash: why is it not needed for a package
uploaded to a given suite, that the commit is reachable in refs/dgit/suite ?
AIUI this is because packages move between suites in the archive without
that move necessarily being immediately
21 matches
Mail list logo
