Re: [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output.

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Nov 15, 2005, 05:10 UTC
Message-ID: <46a038f90511142110x3aa22882j768f33ec1a882dab@mail.gmail.com>
In-Reply-To: <7vsltyvnjf.fsf@assigned-by-dhcp.cox.net>

On 11/15/05, Junio C Hamano <junkio@cox.net> wrote:

Show 6 quoted lines

> Given that you are far more familiar with that part of the code,
> and I suspect I'd be asking your help in archimport as well, a
> repo I can pull from would be more preferable (and sign-off by
> you is certainly an added bonus).  If a public repo is too much
> hassle, however, e-mail forwarding is perfectly fine as well.
> Your choice.

It is _easy_. I've setup a server for git-related paraphernalia at work already ;)

The URL is:
  http://locke.catalyst.net.nz/git/git-martinlanghoff.git/#tojunio

gitweb at:
  http://locke.catalyst.net.nz/gitweb?p=git-martinlanghoff.git;a=summary

That gitweb has per-branch RSS feeds, if you are an rss junkio ;-) you can just subscribe to it...

A word of warning, though: those branches rewind/rebase often, and I won't apologise about it. You should be able to just delete your 'martinlanghoff' head and refetch it. Anyone else reading this... just _don't_ base your work on my branch as it's bound to break.

> BTW, there is no "mana" points involved in deciding if I
> directly pull from somewhere.  Even if that were the case, you
> have accumulated enough of them already ;-).

:-)

/me is happy that you've forgotten about my brown-paper-bag patch with a random character in the middle!

> Although some might find "${\function}" expansion too cute for
> their taste, Keven's code is fine as-is for me.  I launched the
> baloon just wanting to see what others have to say ;-).

Fine w me -- TIMTOWDI. I do understand, however, your interest in having full paths in the usage line to make debugging easier. Whatever is consistent with the project in general.

cheers,

martin