Since comments have stopped, I've updated DPMT policy:
http://python-modules.alioth.debian.org/policy.html
so now (g)it's official.
Cheers,
-Barry
pgpJPM1vPmxy6.pgp
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-22 11:30, Piotr Ożarowski wrote:
>> i have to admit i'm not totally used to an reviewing git patches
>> per mailinglists, and in this case i got lost a little bit what
>> the current draft is. would it be possible to put a complete
>> draf
> i have to admit i'm not totally used to an reviewing git patches per
> mailinglists, and in this case i got lost a little bit what the
> current draft is.
> would it be possible to put a complete draft online somewhere (maybe
> even as an r/o git), in addition to posting the patches on the ml.
g
On Oct 22, 2015, at 08:32 AM, Ben Finney wrote:
>+1
>http://www.slate.com/articles/technology/technology/2011/01/space_invaders.html>
GOML
-Barry
:)
Piotr Ożarowski writes:
> [Barry Warsaw, 2015-10-21]
> > """
> > DPMT requires a pristine-tar branch, and only upstream tarballs can be used
> > to
> > advance the upstream branch. Complete upstream git history should be
> > avoided
> > in the upstream branch.
> > """
>
> just a tiny change: s
[Barry Warsaw, 2015-10-21]
> How about this:
>
> """
> DPMT requires a pristine-tar branch, and only upstream tarballs can be used to
> advance the upstream branch. Complete upstream git history should be avoided
> in the upstream branch.
> """
just a tiny change: s/ / /
--
Piotr Ożarowski
On Oct 21, 2015, at 02:06 PM, Piotr Ożarowski wrote:
>Only version to version upstream changes should be kept in the repository -
>complete upstream git history should be avoided. In order to make it
>easier to cherry-pick upstream commits as patches, add remote repository
>(example below).
>
>
[Barry Warsaw, 2015-10-21]
> What I'm trying to express is the team decision (a couple of debconfs ago) for
> pristine-tars rather than releasing from upstream git. I do want to keep the
> rationale in the policy doc; it's one sentence and it seems to come up often
> enough. Suggestions for bette
> > >> Is policy.rst automatically kept in sync somehow in between
> > >> python-modules.git and http://python-modules.alioth.debian.org/?
> > >
> > >no, I do it by hand (any other team member can do it as well).
> >
> > How?
>
> scp policy.rst alioth:dpmt_home/public_html
rst2html policy.rst >
> >> Is policy.rst automatically kept in sync somehow in between
> >> python-modules.git and http://python-modules.alioth.debian.org/?
> >
> >no, I do it by hand (any other team member can do it as well).
>
> How?
scp policy.rst alioth:dpmt_home/public_html
--
Piotr Ożarowski
On Oct 19, 2015, at 11:59 PM, Piotr Ożarowski wrote:
>[Brian May, 2015-10-19]
>> Is policy.rst automatically kept in sync somehow in between
>> python-modules.git and http://python-modules.alioth.debian.org/?
>
>no, I do it by hand (any other team member can do it as well).
How?
Cheers,
-Barry
Piotr Ożarowski writes:
> no, I do it by hand (any other team member can do it as well).
Just as long as it does happen. My main concern was I saw to different
files, and thought that they would be two different versions. Seems this
is not actually a problem.
--
Brian May
[Brian May, 2015-10-19]
> Barry Warsaw writes:
>
> > * "PMPT" policy
> > http://python-modules.alioth.debian.org/
> > git+ssh://git.debian.org/git/python-modules/tools/python-modules.git
>
> Is policy.rst automatically kept in sync somehow in between
> python-modules.git and http://python-mo
On Oct 17, 2015, at 08:49 PM, Piotr Ożarowski wrote:
>I moved policy.rst to python-modules.git repo (it was available to edit
>by every team member in SVN as well). It's not OK to edit it and push it
>without having a discussion here (on this mailing list) first, though.
I will make a pass throug
On Sat, Oct 17, 2015 at 7:49 PM, Piotr Ożarowski wrote:
> [IOhannes m zmölnig (Debian/GNU), 2015-10-17]
>> since you have already mentioned this a few times: how about changing
>> the policy then, to clearly state that we use GIT only?
>
> yeah, how about changing it? So many people complain about
Piotr Ożarowski writes:
> I moved policy.rst to python-modules.git repo (it was available to edit
> by every team member in SVN as well). It's not OK to edit it and push it
> without having a discussion here (on this mailing list) first, though.
Ok to push to a non-master branch? e.g. post-git-mi
[IOhannes m zmölnig (Debian/GNU), 2015-10-17]
> since you have already mentioned this a few times: how about changing
> the policy then, to clearly state that we use GIT only?
yeah, how about changing it? So many people complain about SVN and
when it comes to do the actual work only one or two ste
17 matches
Mail list logo
