git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/3] fixup remaining cvsimport tests

From
Chris Rorvick <chris@rorvick.com>
Date
Jan 20, 2013, 21:17 UTC
Message-ID
<CAEUsAPbDTUXhz2BoDOwKCjcLS6BQA=jZ6DME4ZDfTDXRL=ZMqA@mail.gmail.com>
In-Reply-To
<20130120192412.GA7498@serenity.lan>
On Sun, Jan 20, 2013 at 1:24 PM, John Keeping <john@keeping.me.uk> wrote:
Show 10 quoted lines
> On Sun, Jan 20, 2013 at 10:57:50AM -0800, Junio C Hamano wrote:
>> This is not a noise, though.
>>
>> Chris, how would we want to proceed?  I'd prefer at some point to
>> see cvsimport-3 to be in sync when the one patched and tested in
>> Eric's repository is proven enough.  Will Eric be the gatekeeper, or
>> will you be sending patches this way as well?
>
> In this case the patch was to the C portion of cvsps, not the Python
> cvs-import, so not relevant for this particular case.

Oh, I think I misunderstood the question. The only time I passed a patch specifically for git-cvsimport.py directly to Eric was before the his patch was in Junio's repository. Unless I'm mistaken, only the second patch Eric sent was actually imported. Subsequent to this I would have submitted any patches for git-cvsimport.py directly to the git list. I just didn't have any--cvsps had several problems that needed to be worked out before it made sense to look at the importer.

In other words, I don't think Eric should be a gatekeeper of this code.
Chris
Previous: John KeepingNext: Chris Rorvick
Message 10 of 16 in “fixup remaining cvsimport tests”
  1. 0/3 fixup remaining cvsimport testsChris Rorvick, Jan 11, 2013
  2. 1/3 t/lib-cvs.sh: allow cvsps version 3.x.Chris Rorvick, Jan 11, 2013
  3. 2/3 t9600: fixup for new cvsimportChris Rorvick, Jan 11, 2013
  4. 3/3 t9604: fixup for new cvsimportChris Rorvick, Jan 11, 2013
  5. John KeepingJan 20, 2013
  6. Chris RorvickJan 20, 2013
  7. John KeepingJan 20, 2013
  8. Junio C HamanoJan 20, 2013
  9. John KeepingJan 20, 2013
  10. Chris RorvickJan 20, 2013
  11. Chris RorvickJan 20, 2013
  12. Chris RorvickJan 21, 2013
  13. Eric S. RaymondJan 21, 2013
  14. Michael HaggertyJan 23, 2013
  15. John KeepingJan 23, 2013
  16. Michael HaggertyJan 24, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.