On Tue, Sep 06, 2016 at 01:05:33PM -0400, Hal Rosenstock wrote: > On 9/6/2016 12:37 PM, Jason Gunthorpe wrote: > > On Tue, Sep 06, 2016 at 09:59:48AM -0400, Hal Rosenstock wrote: > > > >> It would be nice if history from the original repos was > >> preserved/propagated into this combined repo. Is there a reason that > >> wasn't done ? > > > > Of course this was done. I talked about it at length in the first > > email. What are you seeing that makes you think otherwise? > > I was basing my comment based on git log not including all the commits. ?? $ git log | grep -i commit | wc -l 2421 > > Note that git has all sorts of weirdness with rename handling so this > > doesn't always work so well.. eg github's single file history doesn't > > work, but 'git log --follow' mostly does. > > I see git log doesn't show older commits but you can get them with > --follow one file at a time. Right, you cannot do 'git log --follow libibumad/' for instance, that is a documented limitation of git. You can get around this manually... $ git log libibumad/ | grep -i commit [..] 7a47c9614206e790e2e504c22fc698fe96e1bb5b $ git log 7a47c9614206e790e2e504c22fc698fe96e1bb5b [now you see the natural commit list from the original libibumad] The repository is constructed properly, but git's rename handling does not do everything you might want. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
