On Mar 23, Ian Jackson <ijackson@chiark.greenend.org.uk> wrote: > Obviously, for dgit to be useful, it has to define a standard > interchange format. That format has to be patches-applied because > otherwise naive users can't work with the source code properly. Having the alleged needs of naive users dictate the design of our tools looks like a very bad choice to me... I want something that is useful to me, not to mythical random naive users who may want to work on Debian packages without understanding the basics of how they are created. > But that doesn't necessarily mean that a maintainer who likes to work > with patches-unapplied trees has to change their workflow to use dgit. No, I do not want to have patches-applied *repositories*. > I have a work-in-progress dgit branch which will convert, > automatically, a patches-unapplied branch, to a patches-applied > branch, during dgit push. The maintainer never has to look at the > patches-applied branch, but it appears on the dgit git server for > other dgit users to see. I am not sure of what benefits dgit would bring to me if I am not going to use the repositories that it creates. -- ciao, Marco
Attachment:
signature.asc
Description: PGP signature