One thing I think I got wrong in round 1 is the blanket use of
--ancestor-path. Consider the following branch structure, where
upstream has been merged into master several times.
upstream
-----------0----------------.
\______A_________\B___C_ master
for things like status, --ancestor-path makes sense (or is at least
convenient) since it stops at B, rather returning all non-upstream
commits. However, for exporting patches, we really want to catch A
unless it has been merged upstream. In fact is much more likely to be
cherry-picked upstream, which we probably can't easily detect. On the
other hand exporting extra patches is relatively harmeless here, since
we are already relying on dpkg-source to detect our that patches have
been applied.
I'll play around with maybe making ancestor-path optional, but for now
you might want to delete --ancestry-path on line 121 of git-debpatch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
