On Thu, May 10, 2018 at 8:36 AM, Pavel Sanda wrote:
> Joel Kulesza wrote:
> > Is there a way to bring these consistent so a user can clearly see which
> > commits are going to be compared? I understand the ease associated with
> > the HEAD~N approach; however, can that information be put into th
Joel Kulesza wrote:
> Is there a way to bring these consistent so a user can clearly see which
> commits are going to be compared? I understand the ease associated with
> the HEAD~N approach; however, can that information be put into the Version
> Control Log? Alternatively, could a Version Contr
On Thu, May 10, 2018 at 5:35 AM, Pavel Sanda wrote:
> Joel Kulesza wrote:
> > Colleagues:
> >
> > I have a LyX document in a larger git repository that I wish to compare
> > with a previous commit. Other than "counting back" commits, is there a
> way
> > to see precisely which two commits the Ly
Joel Kulesza wrote:
> Colleagues:
>
> I have a LyX document in a larger git repository that I wish to compare
> with a previous commit. Other than "counting back" commits, is there a way
> to see precisely which two commits the LyX documents correspond to that are
> being compared?
If you mean s
Colleagues:
I have a LyX document in a larger git repository that I wish to compare
with a previous commit. Other than "counting back" commits, is there a way
to see precisely which two commits the LyX documents correspond to that are
being compared?
I apologize in advance if I'm overlooking som
