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

Re: [PATCH 4/5] svn-fe: use svn-fe --no-progress in remote-svn-alpha

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 6, 2011, 12:30 UTC
Message-ID
<20110706123044.GR15682@elie>
In-Reply-To
<CALkWK0mrpy2bho9ExHaCSenzZLoEKSo-T0K_FVDz9VtaQcY-2g@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Dmitry Ivankov writes:
Show 8 quoted lines
>> Just disable progress lines for now.
>>
>> Signed-off-by: Dmitry Ivankov <divanorama@gmail.com>
>> ---
>>  contrib/svn-fe/git-remote-svn-alpha |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> Perhaps squash this into the patch that introduces --[no]-progress in svn-fe?

Since git-remote-svn-alpha is a slushy codebase and svn-fe is a little more stable, it seems best to keep patches to the two separate for now. Even so, mentioning remote-svn's needs can still be a useful way to make svn-fe changes easier to understand (which is what I think you are getting at here); thanks for the hint.

Previous: Ramkumar RamachandraNext: Dmitry Ivankov
Message 11 of 12 in “remote-svn-alpha updates”
  1. 0/5 remote-svn-alpha updatesDmitry Ivankov, Jul 5, 2011
  2. 1/5 svn-fe: use svnrdump --quiet in remote-svn-alphaDmitry Ivankov, Jul 5, 2011
  3. 2/5 svn-fe: allow svnadmin instead of svnrdump in svn helperDmitry Ivankov, Jul 5, 2011
  4. Ramkumar RamachandraJul 6, 2011
  5. Dmitry IvankovJul 6, 2011
  6. Ramkumar RamachandraJul 6, 2011
  7. Jonathan NiederJul 6, 2011
  8. 3/5 svn-fe: add a test for remote-svn-alphaDmitry Ivankov, Jul 5, 2011
  9. 4/5 svn-fe: use svn-fe --no-progress in remote-svn-alphaDmitry Ivankov, Jul 5, 2011
  10. Ramkumar RamachandraJul 6, 2011
  11. Jonathan NiederJul 6, 2011
  12. 5/5 svn-fe: use proper refspec in remote-svn-alphaDmitry Ivankov, Jul 5, 2011

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.