Re: Workflow with debian/ in VCS
- To: firstname.lastname@example.org
- Subject: Re: Workflow with debian/ in VCS
- From: Ben Finney <email@example.com>
- Date: Sun, 24 Jul 2011 15:15:40 +1000
- Message-id: <firstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <20110521132003.GA4693@nibiru.local>
Enrico Weigelt <email@example.com> writes:
> I really wonder, why you don't just track everything in a VCS
> like git, set the Debian changes (to the source tree) ontop the
> upstream release tag and simply add the control files ?
> And when a new upstream release comes, simply rebase.
Rebase, or re-writing history, loses valuable information.
I think it's the job of a VCS to preserve that information, and I avoid
workflows that entail routinely losing information.
Not to mention that re-writing a repository's history is inconsiderate
to any downstream branches from the same repository.
\ “Of course, everybody says they're for peace. Hitler was for |
`\ peace. Everybody is for peace. The question is: what kind of |
_o__) peace?” —Noam Chomsky, 1984-05-14 |