martin f krafft wrote:
> Let's assume for a minute that we accept that VCSs are the way
> forward and start to consider how we could track bugs in the VCS,
> alongside the code.
>
> Start to think about it this way, and stuff suddenly neatly aligns,
> at least in my world.
>
> Suddenly you can co
Jelmer Vernooij <[EMAIL PROTECTED]> writes:
> Have you seen bugs everywhere (http://www.bugseverywhere.org) ? It's a
> distributed bug tracker that stores bug information as metadata in VCS
> branches.
I'm currently working on http://bugs.debian.org/477125> a Debian
package for Bugs Everywhere
ht
also sprach Jelmer Vernooij <[EMAIL PROTECTED]> [2008.05.21.1633 +0200]:
> Have you seen bugs everywhere (http://www.bugseverywhere.org)
> ? It's a distributed bug tracker that stores bug information as
> metadata in VCS branches.
Yes, but I didn't remember the name on the plane. :)
--
.''`.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
martin f krafft wrote:
[...]
> What we're trying to do right now is more or less keep track of
> patches in Debian packages. Joey proposes to use bug reports for
> that. It *does* make some sense, but it's far-fetched. Very
> far-fetched. Y
also sprach Joey Hess <[EMAIL PROTECTED]> [2008.05.17.2201 +0100]:
> What if we just decide that changes made to upstream sources[1] qualify
> as a bug? A change might be a bug in upstream, or in the debianisation,
> or in Debian for requiring the change. But just call it a bug.
> Everything else f
5 matches
Mail list logo
