On Fri, Aug 27, 2010 at 02:42:42PM +0200, Michael Prokop wrote: > * Guido Günther <[email protected]> [Fri Aug 27, 2010 at 02:34:40PM +0200]: > > On Fri, Aug 27, 2010 at 01:31:17PM +0200, Michael Prokop wrote: > > > > I've a git-svn clone of a svn repository and want to use git-dch. > > > It works fine in the toplevel directory, but when running git-dch > > > inside a subdirectory it complains with: > > > > foo/x.y is not a git repository > > > > Running 'mkdir .git ; git-dch .... rmdir .git' works though. :) > > > Would be great if git-dch wouldn't check for existence of .git but > > > use another approach for detecting a valid git repository. > > > The aproach is basically correct we could only check for upper level > > directories too - as git itself does. > > > The important part is that we need to fix all tools at once. > > Just noticed this, jepp. > > > Patches are welcome. > > Instead of checking for .git how about executing "git rev-parse --show-cdup" > and if that works it's a git repository, otherwise raise the > GitRepositoryError? The simple check for '.git' is more of a bandaid which needs to go anyway. Combined with --is-bare-repository this makes sense. Thanks for the pointer! -- GUidio
> > > I use gbp with svn like this: > > > http://honk.sigxcpu.org/con/Using_git_svn_and_git_buildpackage_to_build_packages_maintained_in_Subversion.html > > > If --trunk, --tags and --branches are used correctly you should end up > > with .git in the toplevel directory of the repo and you don't run into > > these issues. > > Thanks for the hint, I'm aware of that - though it's not always > possible in my situation. :) > > regards, > -mika- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
