On Wed, Jan 22, 2014 at 1:37 PM, Stephan Beal sgb...@googlemail.com wrote:
On Wed, Jan 22, 2014 at 6:58 PM, Ron Wilson ronw.m...@gmail.com wrote:
Expanding on my suggestion for relative tags like +2 or -3, the
capability to specify a commit relative to an arbitrary specified commit
would
Hello all,
knowing the checkin hash, how can I get in cli the diff introduced by of the
checkin? Similar to what appears in the checkin page on the ui.
Regards,
Lluís.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Wed, Jan 22, 2014 at 3:12 AM, Lluís Batlle i Rossell vi...@viric.namewrote:
Hello all,
knowing the checkin hash, how can I get in cli the diff introduced by of
the
checkin? Similar to what appears in the checkin page on the ui.
I think you have to know both the checkin hash and the
On Wed, Jan 22, 2014 at 06:25:14AM -0500, Richard Hipp wrote:
On Wed, Jan 22, 2014 at 3:12 AM, Lluís Batlle i Rossell
vi...@viric.namewrote:
Hello all,
knowing the checkin hash, how can I get in cli the diff introduced by of
the
checkin? Similar to what appears in the checkin page
If you update your work space to the commit in question, I think you could
do::
fossil diff --from previous
Expanding on my suggestion for relative tags like +2 or -3, the
capability to specify a commit relative to an arbitrary specified commit
would be useful as well.
On Wed, Jan 22, 2014
On Wed, Jan 22, 2014 at 6:58 PM, Ron Wilson ronw.m...@gmail.com wrote:
Expanding on my suggestion for relative tags like +2 or -3, the
capability to specify a commit relative to an arbitrary specified commit
would be useful as well.
There's a potential problem there: when a checkin has
6 matches
Mail list logo
