[darcs-devel] [patch1863] WIP: force PatchSet to always start at Origin

Ganesh Sittampalam bugs at darcs.net
Mon Aug 12 01:34:17 UTC 2019


Ganesh Sittampalam <ganesh at earth.li> added the comment:

Here's a bit of a brute force refactoring to avoid passing
a PatchSet from rebase log.

I don't particularly like it as there's no principle
behind the new 'getLogInfoCore' but it should do the job.
Any better solutions would be welcome.

(as before I haven't tested this, only typechecked it -
I'll run the tests before pushing anything to screened)

1 patch for repository darcs-unstable at darcs.net:screened:

patch 69a11e8e32c629e83503673014d487eb83239fd4
Author: Ganesh Sittampalam <ganesh at earth.li>
Date:   Mon Aug 12 02:32:18 BST 2019
  * refactor the "darcs log" code to accept a list of patches
  
  "rebase log" was faking a PatchSet to call it, which
  violated the invariant observed elsewhere that all
  PatchSets should start from Origin.

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/patch1863>
__________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-preview.txt
Type: text/x-darcs-patch
Size: 4722 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/darcs-devel/attachments/20190812/4070be7c/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: refactor-the-_darcs-log_-code-to-accept-a-list-of-patches.dpatch
Type: application/x-darcs-patch
Size: 45275 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/darcs-devel/attachments/20190812/4070be7c/attachment-0003.bin>
-------------- next part --------------
.





More information about the darcs-devel mailing list