On 8/6/2014 21:00, Andy Bradford wrote:
Thus said B Harder on Wed, 06 Aug 2014 10:41:47 -0700:
Do we have fine-grained control over pulling only specifically rooted
branches?
No, but you can certainly clone the developers clone and inspect his
changes before pulling into your clone
Thus said Warren Young on Thu, 07 Aug 2014 13:50:18 -0600:
This is beginning to sound like my outside contributions feature
request, a.k.a. uber-patch: http://goo.gl/4lLAuY
Yes, it is, and I had that same thought as I typed it, but, it can
already be accomplished with Fossil clone to
On Thu, Aug 7, 2014 at 3:50 PM, Warren Young war...@etr-usa.com wrote:
This is beginning to sound like my outside contributions feature
request, a.k.a. uber-patch: http://goo.gl/4lLAuY
My idea was to allow untrusted outsiders to be able to send a richer
patch file than patch(1) allows, but
On 5-8-2014 23:16, Warren Young wrote:
On 7/26/2014 08:53, Eric Rubin-Smith wrote:
* Code review!
Fossil already provides all the code review I think any nimble team
should need: RSS.
1. Set Fossil up as a server. [1]
It's not even necessary to set Fossil up as a server; you can also
On Tue, Aug 5, 2014 at 11:16 PM, Warren Young war...@etr-usa.com wrote:
I'm not aware of any evidence that an approve-up-front development process
gives better end results than a fix-in-place process.
Just to play Devil's Advocate (and not intended to diminish your thoughtful
and detailed
On Wed, Aug 6, 2014 at 6:36 AM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Aug 5, 2014 at 11:16 PM, Warren Young war...@etr-usa.com wrote:
I'm not aware of any evidence that an approve-up-front development
process gives better end results than a fix-in-place process.
Just to play
On Tue, Aug 5, 2014 at 5:16 PM, Warren Young war...@etr-usa.com wrote:
On 7/26/2014 08:53, Eric Rubin-Smith wrote:
* Code review!
Your talk of state machines suggests that you're instead envisioning a
system where you can't get a checkin into the trunk -- maybe not even into
a
On 8/6/2014 01:49, Martijn Coppoolse wrote:
On 5-8-2014 23:16, Warren Young wrote:
1. Set Fossil up as a server. [1]
It's not even necessary to set Fossil up as a server; you can also run
`fossil rss`
Nice. Thanks for the tip.
[2] A quick glance at src/rss.c in the Fossil sources says
On 8/6/14, Ron W ronw.m...@gmail.com wrote:
On Tue, Aug 5, 2014 at 5:16 PM, Warren Young war...@etr-usa.com wrote:
On 7/26/2014 08:53, Eric Rubin-Smith wrote:
* Code review!
Your talk of state machines suggests that you're instead envisioning a
system where you can't get a checkin into
Thus said Ron W on Wed, 06 Aug 2014 13:14:13 -0400:
When a developer has a change ready for review, she/he sends a review
request with the name of the branch (on his repo). the the integrator
(or an automated process) would then pull that branch so the reviewers
can review if.
Do you mean
Thus said Warren Young on Wed, 06 Aug 2014 12:22:45 -0600:
Out here in the normal software world, I think we are being
presumptuous to use the word engineering. We usually cannot write an
equation to prove our software correct.
The earth trembles as Dijkstra rolls in his grave:
On 8/6/2014 15:27, Andy Bradford wrote:
Thus said Warren Young on Wed, 06 Aug 2014 12:22:45 -0600:
Out here in the normal software world, I think we are being
presumptuous to use the word engineering. We usually cannot write an
equation to prove our software correct.
The earth
Thus said B Harder on Wed, 06 Aug 2014 10:41:47 -0700:
Do we have fine-grained control over pulling only specifically rooted
branches?
No, but you can certainly clone the developers clone and inspect his
changes before pulling into your clone (or pushing directly to main
repository).
On Wed, Aug 6, 2014 at 7:42 PM, Warren Young war...@etr-usa.com wrote:
I'll finish with my original premise: except in areas where software
development is just a way of doing physics or pure mathematics of one sort
or another, you probably are not doing engineering from the start. This is
On 7/26/2014 08:53, Eric Rubin-Smith wrote:
* Code review!
Fossil already provides all the code review I think any nimble team
should need: RSS.
1. Set Fossil up as a server. [1]
2. Go to the Timeline page, and add .rss to the end of the URL. [2]
3. Subscribe to that URL in your feed
On Sat, Jul 26, 2014 at 10:04 PM, Eric Rubin-Smith eas@gmail.com wrote:
Richard Hipp wrote:
Fossil can give you the ticket data as SQL. I think that is probably
about as portable as ticket data is going to get.
+1
... says the top SQL expert between here and the Romulan Neutral Zone.
On Mon, Jul 28, 2014 at 8:13 PM, Nico Williams n...@cryptonector.com
wrote:
Sure, a JSON representation of the same data would be more portable in
some sense, but either way you have a standard representation of
ahem...
[stephan@host:~/cvs/fossil/cwal/s2]$ f json timeline checkin -n 1 -I 2
{
On 27 July 2014 11:04, Eric Rubin-Smith eas@gmail.com wrote:
Fossil *could* support export to JIRA+git in particular, for example, by
providing a tool that (a) exports to JIRA's supported JSON import format,
(b) collects the mapping from the fossil ticket IDs to the JIRA ticket
IDs, then
More seriously, you're comparing a small project like Fossil's
with the capabilities of behemoths like Microsoft.
No, I'm really not. drh was making a claim that users will ALWAYS have to
convert between two database schemas when exporting tickets from one system
to another. He was making a
On Sat, Jul 26, 2014 at 10:53 AM, Eric Rubin-Smith eas@gmail.com
wrote:
By 'code review' here I mean a web-based tool that has a formalized state
machine for (a) uploading code deltas (b) filing and fixing defects against
the uploaded code and (c) having the right set of people sign off.
I'm starting a company with some folks. Their notion of the default choice
for SCM is git + JIRA for bug tracking + some other tool we'd pick for code
review. This is probably quite common. Since the answers to my questions
will probably be interesting to a relatively wide audience, I hope the
On Sat, Jul 26, 2014 at 10:53 AM, Eric Rubin-Smith eas@gmail.com
wrote:
* Export of tickets.
If we want to move away from fossil to a git-based thing in the future, we
can export the source version history, though that is not as trivial as the
Fossil page on the matter makes it seem
I'm on mobile device - please excuse typos/brevity.
I managed a team of about 10 local committers (in my office) and about 10
more remote (across the country).
I had a FreeBSD production environment. I setup a FreeBSD dev/testing
environment where everybody was isolated by jails, and had their
Richard Hipp wrote:
Is there a better story for moving between any two bug tracking
systems? Do there exist any two bug tracking systems in the world were
you can move from one to the other without having to write some scripts to
transform the data?
I can't tell whether you're asking
24 matches
Mail list logo
