On Tue, Jul 26, 2011 at 5:34 PM, Russ Paielli wrote:
> http://www.fogcreek.com/kiln/features/code-reviews.html
>
> It's just something I stumbled across surfing the web. I have no idea how
> good it is or whether it makes any sense at all to add something like this
> to Fossil.
Possibly something
You might want to take a look at this:
http://www.fogcreek.com/kiln/features/code-reviews.html
It's just something I stumbled across surfing the web. I have no idea how
good it is or whether it makes any sense at all to add something like this
to Fossil.
--Russ P.
On Tue, Jul 26, 2011 at 11:13
On Tue, July 26, 2011 8:07 am, Mike Meyer wrote:
> On Mon, 25 Jul 2011 23:20:31 -0700
> Russ Paielli wrote:
>
>> I posted a recommendation for Fossil earlier today on a Scala forum (see
>> my
>> earlier post today on this forum). I got this reply:
>>
>> And [Fossil] is reported to destroy reposit
On Tue, Jul 26, 2011 at 8:13 PM, Ron Wilson wrote:
> As Remigiusz mentioned, tags can be added to a commit to indicate
> Accept/Reject status from the reviewers. If the consesus is to accept
> the code, then your integrator can merge in the accepted changes.
> Since tags can have a value, they ca
On Mon, Jul 25, 2011 at 2:26 PM, Russ Paielli wrote:
> I am wondering how good Fossil is for code review on a large project. (I am
> a Fossil user, but I am currently only using it in the most basic way, for
> my own project with no collaboration.)
If your developers are making commits to their o
On Mon, 25 Jul 2011, Russ Paielli wrote:
And [Fossil] is reported to destroy repositories if someone branches:
http://sheddingbikes.com/posts/1306005291.html
I expect that mr. Shaw will shoot himself in the foot using "git rebase"
or "git push --force" one day and abandon git for something
On Jul 25, 2011, at 20:26 , Russ Paielli wrote:
> I am wondering how good Fossil is for code review on a large project. (I am
> a Fossil user, but I am currently only using it in the most basic way, for
> my own project with no collaboration.)
Fossil has no specialized facilities for code review
On Jul 26, 2011, at 09:07 , Mike Meyer wrote:
>> And [Fossil] is reported to destroy repositories if someone branches:
>> http://sheddingbikes.com/posts/1306005291.html
>>
>> Any comments?
>
> Already discussed at length on the list
> (http://www.mail-archive.com/fossil-users@lists.fossil-scm.o
On Jul 23, 2011, at 01:25 , Richard Hipp wrote:
> An experimental change to implement this is on the server. Add the "brbg"
> query parameter to the timeline method to have the background color set by
> branch name. Add "ubg" to have the background color set by user name.
> Examples:
>
> h
On 07/23/11 01:25, Richard Hipp wrote:
[---]
> I tried Ross's proposed color choosing algorithm but it didn't work out. So
> instead I used the hash to select a Hue in an HSV color space, held the S
> and V fixed, and mapped the result into RGB. The color chooser code is
> here, if you are intere
Hello,
long ago I opened this issue, about links to events not being resolved (thus
appearing in read with no href).
http://fossil-scm.org/index.html/tktview?name=b5efc3a47b
I don't know if I should open a new issue... but the links still don't work at
least for the timeline, checkins, or tiquet
On Tue, July 26, 2011 7:20 am, Russ Paielli wrote:
> I posted a recommendation for Fossil earlier today on a Scala forum (see
> my
> earlier post today on this forum). I got this reply:
>
> And [Fossil] is reported to destroy repositories if someone branches:
> http://sheddingbikes.com/posts/13060
On Mon, 25 Jul 2011 23:20:31 -0700
Russ Paielli wrote:
> I posted a recommendation for Fossil earlier today on a Scala forum (see my
> earlier post today on this forum). I got this reply:
>
> And [Fossil] is reported to destroy repositories if someone branches:
> http://sheddingbikes.com/posts/1
13 matches
Mail list logo
