Pascal Obry <pascal@obry.net> writes:

quoted text
> I'd like to check for example that if a file has been added to the
> remote Subversion repository then it is properly added into a MANIFEST
> file. I'd also like to check some style rules. This would help to
> detect some problems when one has no way to add hooks on the
> Subversion repository.

Are you saying that there may be breakages that is made at the Subversion
side, and you would want to catch it?

What would you do _after_ finding out that somebody screwed up and you
have a borked history on the Subversion side already?

I do not think this belongs to "git svn rebase" (let alone "git rebase",
no way --- you won't rewrite nor reject the upstream even if you find
problems with it).

I understand that you would at least want to notice the damange to the
history that happened at the remote end, and I agree it would make sense
to do something like:

	$ git command-that-updates-the-remote-tracking-branch git-svn
        $ check-history git-svn@{1}..git-svn

The "command-that-updates" could be "svn fetch" or just a simple "fetch".

But the "check-history" script will be very specific to your project, and
I do not think it makes sense to make it a hook to the "command-that-updates".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html