* Norbert Tretkowski wrote:
> * John Goerzen wrote:
> > Darcs has a nice way of pushing patches via e-mail, with GPG
> > signatures even.
>
> That's the only feature I miss after I switched from darcs to
> mercurial.
I just realized that this feature is implemented in the patchbomb
extension, whi
On 06/08/06, Norbert Tretkowski <[EMAIL PROTECTED]> wrote:
* John Goerzen wrote:
> Darcs has a nice way of pushing patches via e-mail, with GPG
> signatures even.
That's the only feature I miss after I switched from darcs to
mercurial.
Norbert
At last someone mentions mercuria
* John Goerzen wrote:
> Darcs has a nice way of pushing patches via e-mail, with GPG
> signatures even.
That's the only feature I miss after I switched from darcs to
mercurial.
Norbert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
On Tue, 2006-08-01 at 14:55 -0500, John Goerzen wrote:
> On Tue, Aug 01, 2006 at 08:31:37PM +0200, Adeodato Simó wrote:
> > Right, bzr is great when you have a designed person to integrate
> > contributor's changes after review.
> >
> > But if you have a set of equal developers, bzr can be also us
On Tue, Aug 01, 2006 at 09:06:19PM +0100, martin f krafft wrote:
> This feature is in development for bzr, called the smart server.
> Just for completeness.
>
> John, are you actually using the workflow you describe for
> maintenance of Debian packages? Single or team maintenance? Could
> you elab
also sprach John Goerzen <[EMAIL PROTECTED]> [2006.08.01.2055 +0100]:
> Darcs has a nice way of pushing patches via e-mail, with GPG signatures
> even. These can be processed in an automated way on the server,
> verified against, for instance, the Debian keyring, and then applied to
> the reposito
On Tue, 01 Aug 2006, John Goerzen wrote:
> Darcs has a nice way of pushing patches via e-mail, with GPG signatures
> even. These can be processed in an automated way on the server,
> verified against, for instance, the Debian keyring, and then applied to
> the repository.
Which would also be a fa
On Tue, Aug 01, 2006 at 08:31:37PM +0200, Adeodato Simó wrote:
> Right, bzr is great when you have a designed person to integrate
> contributor's changes after review.
>
> But if you have a set of equal developers, bzr can be also used in a
> very similar way to Subversion, where all commits go to
8 matches
Mail list logo
