On Tue, Sep 23, 2008 at 08:25:38AM +0200, martin f krafft wrote:
> also sprach Stefano Zacchiroli <[EMAIL PROTECTED]> [2008.07.15.2031 +0200]:
> > I'm a happy (Debian) package maintainer which have just switched
> > most of his packages from svn to git. All nice, finally I can work
> > directly on
also sprach Stefano Zacchiroli <[EMAIL PROTECTED]> [2008.07.15.2031 +0200]:
> I'm a happy (Debian) package maintainer which have just switched
> most of his packages from svn to git. All nice, finally I can work
> directly on a real source code tree instead of fiddling with patch
> management syste
On Tue, Jul 15, 2008 at 08:31:04PM +0200, Stefano Zacchiroli wrote:
> Specifically for Debian: do we have any guideline on how to do that? If
> not it is probably worth to create one ...
For simple patches I maintain a patch-queue branch (which gets rebased
of course) and debian/rules has:
redo-pa
Stefano Zacchiroli wrote:
> Specifically for Debian: do we have any guideline on how to do that? If
> not it is probably worth to create one ...
>
> And finally, the problem of the problems: how about the situation where
> one patch for topic branch is not enough as topic branches have got
> inter
On Tue, Jul 15, 2008 at 01:38:14PM -0500, John Goerzen wrote:
> I don't split out patches, but all my Debian packages live on
> git.debian.org (except software where I'm the upstream, in which case
> it's on my own git server). Using gitweb, people can inspect the
> changelog and download diffs of
I'm a happy (Debian) package maintainer which have just switched most of
his packages from svn to git. All nice, finally I can work directly on a
real source code tree instead of fiddling with patch management system.
Nevertheless, patches are separate in topic branches which enable
knowing the con
