git-svn name

git-svn name

[Eric Wong]

I told somebody about my 'git-svn' program, and of course they asked
where they could read about it.   Since I don't have a website for it,
I Googled for 'git-svn' in hopes that it'd lead me to
contrib/git-svn/git-svn.txt on gitweb.

To my surprise, I found that git-svn was already packaged for several
major distributions.  Of course, it turns out that those binary packages
are actually of git-svnimport.  Oops, maybe I should've checked before
naming my own creation git-svn :x

Of course, I still think git-svn is a good name because it describes
what the program does in as little text as possible.  If anybody has any
suggestions that don't require too much typing while keeping the name
meaningful, feel free to suggest them.

Would distro package maintainers also be willing to add my git-svn
script to their git-svn binary packages when a new release of git is
made, too?  It's quite different from git-svnimport (see
contrib/git-svn/git-svn.txt for details).

-- 
Eric Wong

Re: git-svn name

[Petr Baudis]

Dear diary, on Sun, Mar 26, 2006 at 05:04:25AM CEST, I got a letter
where Eric Wong <normalperson@yhbt.net> said that...
> Would distro package maintainers also be willing to add my git-svn
> script to their git-svn binary packages when a new release of git is
> made, too?  It's quite different from git-svnimport (see
> contrib/git-svn/git-svn.txt for details).

I think the primary purpose of the packages separation are dependencies
- not to make the git package depend on svn and such. So I guess the
packagers won't have a problem adding your script to the git-svn package
(concerning SuSE, I won't at least).

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time.  I think
I have forgotten this before.

Re: git-svn name

[Chris Wright]

* Eric Wong (normalperson@yhbt.net) wrote:
> Would distro package maintainers also be willing to add my git-svn
> script to their git-svn binary packages when a new release of git is
> made, too?  It's quite different from git-svnimport (see
> contrib/git-svn/git-svn.txt for details).

I think your script name is fine.  Best way to handle this is with a
patch to make your git-svn part of the git-svn packaging.

thanks,
-chris