Dear diary, on Sat, Sep 23, 2006 at 06:00:35AM CEST, I got a letter where Shawn Pearce <spearce@xxxxxxxxxxx> said that... > I can see the same concept of ref history being useful even for > core git-rebase and doing it this way would also give it to StGIT > without Catalin needing to change code. In my StGIT tree, I don't want to have arbitrary N-days cutoff point, I want all the patches history preserved at least as long as I carry the patch, because it's just as valuable as the "regular" project history to me. > But it doesn't help git bisect. It's not really all that clear how should bisect work in case of multi-dimensional history. To do it sensibly, I guess you would have to have another command like "stg commitseries" which declares "right now I have the series (patches, their applied/unapplied state and their ordering) in a clearly defined state" and then bisect between those. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html