On Sun, Nov 1, 2009 at 9:21 PM, David Brownell <davi...@pacbell.net> wrote: > On Sunday 01 November 2009, Řyvind Harboe wrote: >> >> Hmm.... how do I read out which version a git patch is relative to? >> > >> > git show --pretty=raw 818cedaff >> > >> > instead of just "git show" (or "git log" etc). That includes >> > parent IDs ... possibly more than one for merge commits, as in >> > the example above. >> >> I would have expected a patch to show what the parent id was... > > The notion of a "parent" is fuzzy ... if the patch can > apply to a hundred different incarnations of a tree, > which one is "the" parent? > > So the only time "parent" really makes sense is when > talking about a particular integration history: in > this branch, it merged right here. > > Historically, source code patches have been decoupled > from base versions specifically so they can apply to > as many versions as need that specific change/bugfix.
My thinking was that rebasing would be *much* easier if it was possible to tell what the parent to that patch was... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
