sapling/tests/test-mq-qimport.out

% qimport non-existing-file
abort: unable to read non-existing-file
% import email
adding email to series file
applying email
now at: email
% hg tip -v
changeset:   0:1a706973a7d8
tag:         email
tag:         qbase
tag:         qtip
tag:         tip
user:        Username in patch <test@example.net>
date:        Thu Jan 01 00:00:00 1970 +0000
files:       x
description:
First line of commit message.

More text in commit message.


popping email
patch queue now empty
% import URL
adding url.diff to series file
url.diff
% import patch that already exists
abort: patch "url.diff" already exists
applying url.diff
now at: url.diff
foo
popping url.diff
patch queue now empty
% qimport -f
adding url.diff to series file
applying url.diff
now at: url.diff
foo2
popping url.diff
patch queue now empty
% build diff with CRLF
adding b
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
% qimport CRLF diff
adding b.diff to series file
applying b.diff
now at: b.diff
% try to import --push
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
adding another.diff to series file
applying another.diff
now at: another.diff
patch b.diff finalized without changeset message
patch another.diff finalized without changeset message
qimport: report filename in case of IOError The old behaviour was to say "abort: unable to read" since the patchname variable was always None. 2008-08-26 02:04:18 +04:00			`% qimport non-existing-file`
Catch both IOError and OSError, fix regression introduced by 0018648194a9 2008-11-26 20:23:35 +03:00			`abort: unable to read non-existing-file`
mq: Parse commit message after we find start of changeset patch patch.extract extracts just the message below HG changeset patch. So to not parse comments above the patch, we reset the message if we find a changeset patch as we know the commit message comes after the changeset patch data. This is similar to the behavior of patch.extract. The drawback of this approach, after a qref -e the comment above HG changeset patch is gone. Without this patch the message would become part of the commit message in the HG changset patch part. 2009-07-28 17:36:28 +04:00			`% import email`
			`adding email to series file`
			`applying email`
			`now at: email`
			`% hg tip -v`
			`changeset: 0:1a706973a7d8`
			`tag: email`
			`tag: qbase`
tags: return tags in sorted order This makes log and summary have less arbitrary tag ordering and also groups similar tags together, such as the mq tags. 2010-04-26 23:58:36 +04:00			`tag: qtip`
			`tag: tip`
mq: Parse commit message after we find start of changeset patch patch.extract extracts just the message below HG changeset patch. So to not parse comments above the patch, we reset the message if we find a changeset patch as we know the commit message comes after the changeset patch data. This is similar to the behavior of patch.extract. The drawback of this approach, after a qref -e the comment above HG changeset patch is gone. Without this patch the message would become part of the commit message in the HG changset patch part. 2009-07-28 17:36:28 +04:00			`user: Username in patch <test@example.net>`
			`date: Thu Jan 01 00:00:00 1970 +0000`
			`files: x`
			`description:`
			`First line of commit message.`

			`More text in commit message.`


Merge with crew-stable 2009-08-01 02:36:22 +04:00			`popping email`
mq: Parse commit message after we find start of changeset patch patch.extract extracts just the message below HG changeset patch. So to not parse comments above the patch, we reset the message if we find a changeset patch as we know the commit message comes after the changeset patch data. This is similar to the behavior of patch.extract. The drawback of this approach, after a qref -e the comment above HG changeset patch is gone. Without this patch the message would become part of the commit message in the HG changset patch part. 2009-07-28 17:36:28 +04:00			`patch queue now empty`
mq: let qimport read patches from URLs 2008-10-19 03:40:01 +04:00			`% import URL`
			`adding url.diff to series file`
			`url.diff`
mq: make qimport -f work properly. Closes issue1255. From Bernhard Leiner. 2008-10-19 04:29:45 +04:00			`% import patch that already exists`
			`abort: patch "url.diff" already exists`
			`applying url.diff`
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. 2009-01-03 19:15:21 +03:00			`now at: url.diff`
mq: make qimport -f work properly. Closes issue1255. From Bernhard Leiner. 2008-10-19 04:29:45 +04:00			`foo`
mq: qpop now tells which patches are popped When navigating through a patch series by qpushing and qpopping it was easy to get lost because qpop was silent. I found myself often running qnext after qpop to see which patch I just dropped - especially if I was about to qrm it. This patch makes qpop more symmetric to qpush by showing which patches are applied/"unapplied". I think it is a good change even though it changes output by adding a new line of output. 2009-07-10 01:59:03 +04:00			`popping url.diff`
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. 2009-01-03 19:15:21 +03:00			`patch queue now empty`
mq: make qimport -f work properly. Closes issue1255. From Bernhard Leiner. 2008-10-19 04:29:45 +04:00			`% qimport -f`
			`adding url.diff to series file`
			`applying url.diff`
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. 2009-01-03 19:15:21 +03:00			`now at: url.diff`
mq: make qimport -f work properly. Closes issue1255. From Bernhard Leiner. 2008-10-19 04:29:45 +04:00			`foo2`
mq: qpop now tells which patches are popped When navigating through a patch series by qpushing and qpopping it was easy to get lost because qpop was silent. I found myself often running qnext after qpop to see which patch I just dropped - especially if I was about to qrm it. This patch makes qpop more symmetric to qpush by showing which patches are applied/"unapplied". I think it is a good change even though it changes output by adding a new line of output. 2009-07-10 01:59:03 +04:00			`popping url.diff`
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. 2009-01-03 19:15:21 +03:00			`patch queue now empty`
mq: qimport must read patches in binary mode 2008-02-07 01:09:13 +03:00			`% build diff with CRLF`
			`adding b`
			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
			`% qimport CRLF diff`
			`adding b.diff to series file`
			`applying b.diff`
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. 2009-01-03 19:15:21 +03:00			`now at: b.diff`
mq: add -P/--push option to qimport 2009-05-12 13:15:54 +04:00			`% try to import --push`
			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
			`adding another.diff to series file`
			`applying another.diff`
			`now at: another.diff`
mq: warn about finalizing patches without cset message 2009-06-19 14:37:29 +04:00			`patch b.diff finalized without changeset message`
			`patch another.diff finalized without changeset message`