So I created the 'autosetup' branch and added a commit which drh then merged to
trunk.
Is that branch now defunct? If I want to propose some more, related changes,
do I create a new branch, say autosetup2, or do I continue or resurrect the
autosetup branch?
If so, how?
Thanks,
Steve
--
µWeb:
On Fri, Jul 22, 2011 at 7:57 AM, Steve Bennett ste...@workware.net.auwrote:
So I created the 'autosetup' branch and added a commit which drh then
merged to trunk.
Is that branch now defunct? If I want to propose some more, related
changes,
do I create a new branch, say autosetup2, or do I
On Jul 22, 2011, at 13:57 , Steve Bennett wrote:
So I created the 'autosetup' branch and added a commit which drh then merged
to trunk.
Is that branch now defunct?
If your changes are well integrated into trunk, and you're not continuing
development in isolation from trunk, you should
On Jul 22, 2011, at 14:46 , Richard Hipp wrote:
fossil commit --branch autosetup --bgcolor '#91d680'
The --bgcolor on the last commit is optional. But it is nice to have color
on branches. If you forget it, it can be added later using the Edit feature
of the UI. (That's how I added
On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
l...@maxnet.org.plwrote:
By the way: this is one of the more cumbersome things about the UI. I'd
really like to see this done automatically. But then again, I don't feel
like wasting my time on this, so I don't expect anyone to waste
On Jul 22, 2011, at 15:50 , Stephan Beal wrote:
On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski
l...@maxnet.org.plwrote:
By the way: this is one of the more cumbersome things about the UI. I'd
really like to see this done automatically. But then again, I don't feel
like wasting my
On Fri, Jul 22, 2011 at 9:50 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jul 22, 2011 at 2:54 PM, Remigiusz Modrzejewski l...@maxnet.org.pl
wrote:
By the way: this is one of the more cumbersome things about the UI. I'd
really like to see this done automatically. But then again, I
At 05:54 AM 7/22/2011, Remigiusz Modrzejewski wrote:
On Jul 22, 2011, at 14:46 , Richard Hipp wrote:
The --bgcolor on the last commit is optional. But it is nice
to have color on branches.
By the way: this is one of the more cumbersome things about the
UI. I'd really like to see this
On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig r...@cheshireeng.com wrote:
It would be nice if branches had a default color distinct from
the trunk. ... One way to do that that *might* be ... generate a hash of
the branch tag
name and use it for the color.
Do you have a suggested hash
On Fri, Jul 22, 2011 at 03:14:38PM -0400, Richard Hipp wrote:
On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig r...@cheshireeng.com wrote:
It would be nice if branches had a default color distinct from
the trunk. ... One way to do that that *might* be ... generate a hash of
the branch tag
2011/7/22 Lluís Batlle i Rossell virik...@gmail.com
Maybe my opinion is of little value, but I like what fossil is currently
doing
with branches and colors. I use it since months and I'm very happy with it,
not
needing anything more.
Basically everything Fossil's added since early 2008 has
At 12:14 PM 7/22/2011, Richard Hipp wrote:
On Fri, Jul 22, 2011 at 3:07 PM, Ross Berteig
r...@cheshireeng.com wrote:
It would be nice if branches had a default color distinct from
the trunk. ... One way to do that that *might* be ... generate a
hash of the branch tag name and use it for
On Fri, Jul 22, 2011 at 11:07 PM, Ross Berteig r...@cheshireeng.com wrote:
For skins that are dark text on white background, then using the
existing MD5 hash on the tag name, picking a convenient three;
...
it would make an entertaining experiment, whether or not it turns out to be
useful in
13 matches
Mail list logo
