[Debian-olpc-devel] How _should_ we import new changes into git?
holger at layer-acht.org
Thu Jan 15 22:21:29 UTC 2009
(I have quite a lot of backlog in various fields, so I just briefly comment on
one aspect here. I plan to comment and do more...)
On Dienstag, 13. Januar 2009, Jonas Smedegaard wrote:
> My current plan is to move from the current undocumented Git packaging
> to using topgit. Topgit is driven by similar packaging ideals as I have
> had with the current one, and has the great benefit of being documented
> and potentially will become more sidely used within Debian due to active
> promotion by its author Martin Krafft, a generally aknowledged Debian
I think that's a great plan, thanks!
And even though I agree that the current packaging is not easy for newcomers,
I have to say that I found README.packaging to be very well written and
working nicely! :)
But more documentation and a standardized workflow is definitly even better!
I assume this is post-lenny stuff, which shouldn't be that far anyway.
Speaking of which, bugfixes can still make it into lenny, especially if bugs
are filed and if the diff to the version in testing is reasonable and
reviewable - whether it's called "new upstream" is not that important, it's
the diff really :)
Which reminds me of
- afaik sugar, sugar-base and sugar-hulahop should really migrate to lenny,
while for the rest its not critical, right?
(This mail got longer than I thought :)
Holger, guess I will read the rest of the mails in this folder now too ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/debian-olpc-devel/attachments/20090115/5cc9d377/attachment.pgp
More information about the Debian-olpc-devel