vcsbase: refactor status output signal in VCSBaseClient

There is now a clear distinction between the basic status command
and the status command used to emit parsed output

Change-Id: Ie398a866ffcd8f4cc33b864ddbe23ce9d2e97437
Merge-request: 358
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>
Reviewed-on: http://codereview.qt.nokia.com/3337
This commit is contained in:
cerf
2011-08-22 15:33:03 +00:00
committed by Tobias Hunger
parent 0dcd66ef46
commit a8fc5e2134
5 changed files with 8 additions and 7 deletions

View File

@@ -396,11 +396,11 @@ void VCSBaseClient::status(const QString &workingDir, const QString &file)
enqueueJob(job);
}
void VCSBaseClient::statusWithSignal(const QString &repositoryRoot)
void VCSBaseClient::emitParsedStatus(const QString &repository, const QStringList &extraOptions)
{
QStringList args(vcsCommandString(StatusCommand));
args << statusArguments(QString());
QSharedPointer<VCSJob> job(new VCSJob(repositoryRoot, args, VCSJob::RawDataEmitMode));
args << extraOptions;
QSharedPointer<VCSJob> job(new VCSJob(repository, args, VCSJob::RawDataEmitMode));
connect(job.data(), SIGNAL(rawData(QByteArray)), this, SLOT(statusParser(QByteArray)));
enqueueJob(job);
}