El 19/12/08 09:13 Guido Günther escribió: > On Thu, Dec 18, 2008 at 04:15:54PM -0300, Felipe Sateler wrote: > > If --git-export-dir is enabled at the same time than --git-ignore-new, > > then any uncommited changes will not be part of the new package. If, on > > the other hand, --git-export-dir is not enabled but --git-ignore-new is, > > then uncommited changes will be part of the new package. > > > > I would prefer if uncommited changes are always taken into account, but > > it's not that important as long as behaviour is consistent. > > The behaviour is consistent: ignore-new only "discards" warnings about > uncommitted changes in you source tree. From the manpage: > > | Build the .diff.gz and debian package although there are uncommitted > | changes in the source tree. > > It has nothing to do with what will be part of the package or not. You > can take "uncommitted" changes into account by adding them to the index.
It is inconsistent. With --git-export-dir you are building HEAD, without it you are building the working copy. This is an important difference. > You can even export a completely different tree using --git-export. > Cheers, > -- Guido > > P.S.: I'm also thinking about adding a --git-export=WC (working copy) > since others have asked for this too and I think it would also solve > your problem. Probably. I would just make it default. Saludos, Felipe Sateler
signature.asc
Description: This is a digitally signed message part.
