Re: Workflow with debian/ in VCS
- To: debian-mentors@lists.debian.org
- Subject: Re: Workflow with debian/ in VCS
- From: Enrico Weigelt <weigelt@metux.de>
- Date: Fri, 6 Jan 2012 20:00:12 +0100
- Message-id: <[🔎] 20120106190012.GA5692@mailgate.onlinehome-server.info>
- Reply-to: weigelt@metux.de
- In-reply-to: <87d3h0s1hf.fsf@benfinney.id.au>
- References: <87tycw58ev.fsf@vostro.rath.org> <87k4drh4jx.fsf@benfinney.id.au> <87pqnilisi.fsf@inspiron.ap.columbia.edu> <87ei3yf8wo.fsf@benfinney.id.au> <8762p96tjo.fsf@inspiron.ap.columbia.edu> <87hb8setz5.fsf@benfinney.id.au> <87zkmkds65.fsf@inspiron.ap.columbia.edu> <871uzue6cr.fsf@benfinney.id.au> <20110521132003.GA4693@nibiru.local> <87d3h0s1hf.fsf@benfinney.id.au>
* Ben Finney <ben+debian@benfinney.id.au> schrieb:
> Enrico Weigelt <weigelt@metux.de> 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.
Which information exactly ?
> Not to mention that re-writing a repository's history is inconsiderate
> to any downstream branches from the same repository.
Well, they could also rebase per default.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
Reply to: