Requirements gathering for new package source control
Josh Boyer
jwboyer at gmail.com
Tue Jun 10 12:23:19 UTC 2008
On Tue, 10 Jun 2008 02:36:27 +0200
Karel Zak <kzak at redhat.com> wrote:
> On Mon, Jun 09, 2008 at 02:19:38PM -0400, Jesse Keating wrote:
> > Thank you all for your thoughtful consideration.
>
> - be able to easily rebase/refresh a patch
That's pretty outside the scope of any SCM we deploy. Use tools like
quilt.
> - be able to keep track of details about patches (author, committer,
> some special marks (e.g. "signed-of-by", "reviewed-by", ...)
You can do this in the patches themselves.
> - be able to generate statistics about patches (diffstat)
Erm... just use diffstat? What does that have to do with the SCM?
> - be able to generate change logs
>
> - be able to generate patches (to avoid unwanted "creativity", it'd
> be nice to use same format for all Fedora patches)
Generate patches from what? We don't store exploded tarballs. We
store tarballs and patches.
josh
More information about the fedora-devel-list
mailing list