Thibaut Paumard writes ("Re: RFC: DEP-14: Recommended layout for Git packaging
repositories"):
> [patches applied vs unapplied]
>
> However, we should perhaps strongly recommend that this choice be
> documented in debian/README.sources.
I think it would be better to document this by the use of different
branch names. It is, after all, possible to make both patches-applied
and patches-unapplied branches for the same package. For example, if
a package's maintainer team use patches-unapplied, a dgit user will
still see patches-applied. A note in README.sources is (a) in the
wrong place because it attaches not to the particular git branch but
to the whole contents and (b) not machine-readable.
> I think the only workflow that newcomers and NMUers should be required
> to learn is the one that involves quilt, they should not be expected to
> learn (e.g.) dgit in addition. [...]
I certainly don't think people should be expected to learn dgit in
addition to other tools. I am trying to get to the point where
1. they can learn dgit _instead_ of _all_ other tools[1] 2. no-one else
needs to know that this is going on unless they decide to start using
dgit too.
[1] I'm assuming they know git already, and that they're trying to do
NMUs or be a derivative (public or private).
Ian.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/21604.34838.928787.815...@chiark.greenend.org.uk
