If you have CVS as a source, then it's normal for Tailor to attempt to
replay the last changeset.
With a git target that seems to work OK except that you can end up
with an empty commit with the same log message, which is annoying.
A quick hack is the following which just runs "git status". If that
returns a non-zero status, then there's nothing to commit. (I guess
there are other possible error reasons---I'm making no attempt to
catch those.)
New patches:
[git no-change commit check
[EMAIL PROTECTED] {
hunk ./vcpx/repository/git/target.py 80
+ try:
+ self.repository.runCommand(['status'])
+ except Exception, e:
+ self.log.info("git-status returned an error---assuming nothing to do")
+ return
+
}
Context:
[Removed trailing space from the assert, since we just did a .rstrip()
[EMAIL PROTECTED]
[Remove microseconds from the timestamp, at monotone commit time
[EMAIL PROTECTED]
[bzrlib-pull-result-object
Wouter van Heyst <[EMAIL PROTECTED]>**20070428151313]
[python2.5-unittest-api-fix
Wouter van Heyst <[EMAIL PROTECTED]>**20070428150020]
[bazaar-ng-renaming
Wouter van Heyst <[EMAIL PROTECTED]>**20070428143747
What was formerly know as Bazaar-NG is no longer the next generation, but the current one.
See http://bazaar-vcs.org/Baz1x and http://bazaar-vcs.org/Branding.
]
[Create the pre-revprop-change hook only when svn repository is local
[EMAIL PROTECTED]
[Typo
[EMAIL PROTECTED]
[TAG Version 0.9.28
[EMAIL PROTECTED]
Patch bundle hash:
ec6020ad0d323ced7c9ff66efcb310b7dfd193a4
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
