On Tue, Jan 6, 2015 at 6:41 AM, Matt Welland estifo...@gmail.com wrote:
+1 IMHO this is a good idea. How technically feasible it is I have no idea.
agreed. AFAIK, branches currently do not use the VALUE part of the tag.
Perhaps such a description could be set there when making a branch, e.g.:
On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal sgb...@googlemail.com wrote:
agreed. AFAIK, branches currently do not use the VALUE part of the tag.
Perhaps such a description could be set there when making a branch, e.g.:
fossil commit -b new-branch -d branch description -m commit message
On 1/6/15, Ron W ronw.m...@gmail.com wrote:
On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal sgb...@googlemail.com wrote:
agreed. AFAIK, branches currently do not use the VALUE part of the tag.
Perhaps such a description could be set there when making a branch, e.g.:
fossil commit -b
On Tue, Jan 6, 2015 at 11:50 AM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Jan 6, 2015 at 5:12 PM, Ron W ronw.m...@gmail.com wrote:
The sym- one not having a value. Strange to me that 2 tags would be
used (I would have thought only the branch tag), but looks like the
sym- tag could
On Tue, Jan 6, 2015 at 5:12 PM, Ron W ronw.m...@gmail.com wrote:
The sym- one not having a value. Strange to me that 2 tags would be used
(I would have thought only the branch tag), but looks like the sym- tag
could be used to hold a branch description.
One downside: this precludes modifying
On Jan 4, 2015, at 10:55 AM, Philip Bennefall phi...@blastbay.com wrote:
I don't know what a lot of the branches are and I have no obvious way of
finding out.
If it’s a temporary branch, e.g. to develop a risky feature before it gets into
good enough shape that it can be committed to the
+1 IMHO this is a good idea. How technically feasible it is I have no idea.
On Jan 4, 2015 10:59 AM, Philip Bennefall phi...@blastbay.com wrote:
Hi all,
I have a quick suggestion to present. While browsing the SqLite timeline,
it struck me that I don't know what a lot of the branches are and
Hi all,
I have a quick suggestion to present. While browsing the SqLite
timeline, it struck me that I don't know what a lot of the branches are
and I have no obvious way of finding out. I was thinking that it might
be nice to be able to specify an optional description for a given
branch. The
8 matches
Mail list logo
