Not a bad idea -- this part of the description: <<Furthermore, all shunned artifacts (but not the shunning list itself) are removed from the repository whenever the repository is reconstructed using the "rebuild" command.>>
may roughly be what we're looking for. We happen to be applying to a specific artifact only (tip of branch) which shouldn't be any worse than shunning in the middle of a branch, and may be simpler (barring the fact that a tip will have to be properly identified as a "tip"). Otherwise, there may be clues for what cards/blobs to target -- I also presume that the rebuild (for the case of shun) is to re-rationalize dependencies down the chain -- which won't be necessary w/ working on a tip (?) -bch On 10/28/14, Ron W <ronw.m...@gmail.com> wrote: > On Tue, Oct 28, 2014 at 2:21 PM, Stephan Beal <sgb...@googlemail.com> > wrote: > >> On Tue, Oct 28, 2014 at 7:14 PM, B Harder <brad.har...@gmail.com> wrote: >>> >>> 3) I can't think of anything else... >>> >> >> You will. >> > > Perhaps looking at how shunning works would help > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
