> > mypatch.diff ends up in  ~/patches not in ~/projects/quilt/patches
> >
> > creating a patches directory in the current directory before calling
> > quilt new seems to solve the issue.
> 
> Yes. People have asked for his behavior. Originally the new command always
> assumed that the current directory was the topmost directory, while all other
> commands worked from sub-directories. That was changed though.

That sounds good.

> > Is there another way to avoid the issue? E.g. by adding a tag file in
> > the non quilt 'patches' directory?
> 
> I don't think that would be practical. I didn't have this problem often...

One way to solve the problem is to give more information by displaying
in which directory the patch was added. No more surprises.

Jerome


_______________________________________________
Quilt-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/quilt-dev

Reply via email to