On Sun, Jan 15, 2006 at 10:31:15PM -0800, Justin Patrin wrote:
On 1/15/06, Nathaniel Smith [EMAIL PROTECTED] wrote:
If you do go the external program direction, it might be worthwhile
to see if it can be made somewhat general; most of the code involved
in importing from BK is probably the
Richard Levitte - VMS Whacker [Sunday 15 January 2006] :
Hi,
it seems monotone-viz has a problem with refresh, and crashes. The
output I got is attached.
Ouch. Is it reproducible ? You simply press the Refresh button and it
crashes right away ?
I don't know even where to begin
On Mon, Jan 16, 2006 at 10:50:09AM +0300, Petr Ovtchenkov wrote:
telnet www.venge.net 5253
Trying 66.96.28.3...
You may have missed a recent announcement on the mailing list.
http://lists.gnu.org/archive/html/monotone-devel/2006-01/msg00053.html
The main development line of monotone has
In message [EMAIL PROTECTED] on Mon, 16 Jan 2006 10:44:04 +0100, Olivier
Andrieu [EMAIL PROTECTED] said:
oandrieu Richard Levitte - VMS Whacker [Sunday 15 January 2006] :
oandrieu
oandrieu it seems monotone-viz has a problem with refresh, and
oandrieu crashes. The output I got is
Bruce Stephens [EMAIL PROTECTED] writes:
[...]
However, reviewing before integration isn't that unusual. Aegis is
an obvious example, but GNU Arch people seem to work similarly:
someone develops in their archive, and when they've got something
they think is worth merging they say so, and
Nathaniel Smith wrote:
On Sun, Jan 15, 2006 at 02:16:40PM +0100, Richard Levitte - VMS Whacker wrote:
OK, I guess my next thing will be to look at the source, because I
just can't understand what selection criteria it uses. For example,
there are a number of F() used in safe_map.hh, but
I think having another flame war with LM is pointless -- they didn't
touch Andrew because he is under the cover of OSDL.
So external tool is still safer. Especially given that this is a one
time task. I mean nobody uses BK anymore so this tool'd be used only for
one-time conversion from BK to
Nathaniel Smith wrote:
As I understand, tailor does work with monotone as both a source and a
target; but tailor can only handle linear histories. Even if
transferring from one DAG VCS to another, it has to throw away
everything except a single linear subgraph.
This could presumably be fixed.
On Monday 16 January 2006 13:34, Daniel Carosone wrote:
On Mon, Jan 16, 2006 at 10:50:09AM +0300, Petr Ovtchenkov wrote:
telnet www.venge.net 5253
Trying 66.96.28.3...
You may have missed a recent announcement on the mailing list.
See http://lists.gnu.org/archive/html/monotone-devel/2006-01/msg00123.html
Peter Simons wrote:
Nathaniel Smith writes:
Monotone 0.26pre1 has been released.
I tried to connect to venge.net to get the revision tree,
but the port seems to be blacklisted:
| $ telnet venge.net 5253
| Trying
Timothy Brownawell [EMAIL PROTECTED] writes:
[...]
There's not really a good way. The closest is:
monotone disapprove W -b prj.release
Merge branch prj.release .
but I think it won't be happy when you eventually do decide to merge a
decendant of W into the release branch.
Won't it? Why
Daniel Carosone spake unto us the following wisdom:
On Sun, Jan 15, 2006 at 10:31:13PM -0500, Yury Polyanskiy wrote:
This won't handle all situations: suppose a merge revision that adds a
file. I can't direct monotone to add a new file via merge hook.
Yeah, but on the other hand I don't
If I have 3 revisions of A, B, and W in a single branch of
prj.release, with history graph of: A-B, A-W
Then monotone reports that there're two heads, B and W, in the branch
of prj.release.
Let's say revision W is mistakenly checked into the branch of
prj.release and should have had checked into
Nathaniel Smith writes:
Monotone 0.26pre1 has been released.
I tried to connect to venge.net to get the revision tree,
but the port seems to be blacklisted:
| $ telnet venge.net 5253
| Trying 66.96.28.3...
| telnet: Unable to connect to remote host: No route to host
However:
| $ telnet
On Monday 16 January 2006 21:46, Peter Simons wrote:
Nathaniel Smith writes:
Monotone 0.26pre1 has been released.
I tried to connect to venge.net to get the revision tree,
but the port seems to be blacklisted:
| $ telnet venge.net 5253
| Trying 66.96.28.3...
| telnet: Unable to
Drakie Awita [EMAIL PROTECTED] writes:
If I have 3 revisions of A, B, and W in a single branch of
prj.release, with history graph of: A-B, A-W
Then monotone reports that there're two heads, B and W, in the branch
of prj.release.
Let's say revision W is mistakenly checked into the branch of
On Mon, Jan 16, 2006 at 10:12:37AM +0100, Christof Petig wrote:
I waited the weekend for you to comment on my recently finished
sqlite3.binary port to 0.26.
How do you feel about using it in mainline? It is ready AFAICT.
- not for 0.26 we already changed enough?
- directly after 0.26 is
On Mon, 2006-01-16 at 12:20 -0800, Drakie Awita wrote:
If I have 3 revisions of A, B, and W in a single branch of
prj.release, with history graph of: A-B, A-W
Then monotone reports that there're two heads, B and W, in the branch
of prj.release.
Let's say revision W is mistakenly checked
Richard Levitte writes:
[There's] a blatantly obvious lack of information on what
I believe to be the central point for anyone who seeks
information: http://www.venge.net/monotone/.
I agree; it would be a good idea to update the self-hosting
pages.
That wouldn't have helped me either
On Mon, 2006-01-16 at 10:12 +0100, Christof Petig wrote:
Hi Nathaniel,
I waited the weekend for you to comment on my recently finished
sqlite3.binary port to 0.26.
How do you feel about using it in mainline? It is ready AFAICT.
- not for 0.26 we already changed enough?
- directly after
Daniel Carosone wrote:
On Sun, Jan 15, 2006 at 09:21:27PM -0500, Yury Polyanskiy wrote:
The other way is to hack SP and make it call regular monotone commands.
In this latter case, of course it'd be nice if the tool worked with
standard monotone releases, not some specially patched ones. So I'm
21 matches
Mail list logo
