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

Re: [PATCH] git-svn: Add a svn-remote.<name>.pushurl config key

From
Alejandro R. Sedeño <asedeno@mit.edu>
Date
Apr 6, 2011, 12:56 UTC
Message-ID
<4D9C6309.8080809@mit.edu>
In-Reply-To
<4D9C6023.6040305@drmicha.warpmail.net>
On 4/6/2011 8:44 AM, Michael J Gruber wrote:
Show 17 quoted lines
> Alejandro R. Sedeño venit, vidit, dixit 05.04.2011 22:15:
>> > Similar to the 'remote.<name>.pushurl' config key for git remotes, the
>> > 'pushurl' key is treated the same as the 'url' key. This is distinct
>> > from the 'commiturl' key, which is defined to be a full svn path.
>> > 
>> > This is necessary if you want to be able to commit to multiple branches.
> Maybe one can understand this remark after reading the whole thread, but
> reading it as a commit message I'm wondering: Huh? How can I have been
> doing it then without pushurl?
> 
> Also, "treated the same as the url" makes a reader wonder why we have
> two names for the same.
> 
> The point of pushurl is that you can use a passwordless transport for
> fetches and another transport for pushes. The standing assumption is
> that both urls point in fact at the same repo. Weird things can happen
> if not. Is that assumption the same for your svn pushurl?

Yes, that is the idea. I will rephrase the commit message and documentation to be clearer when I send the next version of this patch.

When I say, "treated the same as the url," what I mean to say is that any manipulations that would be done to 'url' are also done to 'pushurl', such as appending '/trunk' or '/branches/<branch-name>/' if necessary, which does not happen with commiturl since it is a full snv path.

-Alejandro
Previous: Michael J GruberNext: Alejandro R. Sedeño
Message 23 of 33 in “[PATCHv2 0/2] a couple of git-svn patches”
  1. Alejandro R. SedeñoApr 4, 2011
  2. 1/2 git-svn: Fix the commit-url config to be the base url, just like the url configAlejandro R. Sedeño, Apr 4, 2011
  3. Eric WongApr 4, 2011
  4. James Y KnightApr 4, 2011
  5. Eric WongApr 4, 2011
  6. Alejandro R. SedeñoApr 5, 2011
  7. git-svn: Add a svn-remote.<name>.pushurl config keyAlejandro R. Sedeño, Apr 5, 2011
  8. Alejandro R. SedeñoApr 5, 2011
  9. Eric WongApr 5, 2011
  10. Michael J GruberApr 6, 2011
  11. Alejandro R. SedeñoApr 6, 2011
  12. Michael J GruberApr 6, 2011
  13. git-svn: Add a svn-remote.<name>.pushurl config keyAlejandro R. Sedeño, Apr 6, 2011
  14. Michael J GruberApr 6, 2011
  15. Alejandro R. SedeñoApr 6, 2011
  16. Michael J GruberApr 6, 2011
  17. git-svn: Add a svn-remote.<name>.pushurl config keyAlejandro R. Sedeño, Apr 8, 2011
  18. Junio C HamanoApr 8, 2011
  19. Michael J GruberApr 8, 2011
  20. Jeff KingApr 8, 2011
  21. Eric WongApr 9, 2011
  22. Michael J GruberApr 6, 2011
  23. Alejandro R. SedeñoApr 6, 2011
  24. 2/2 git-svn: Cache results of running the executable "git config"Alejandro R. Sedeño, Apr 4, 2011
  25. Eric WongApr 4, 2011
  26. Junio C HamanoApr 5, 2011
  27. Jeff KingApr 8, 2011
  28. Junio C HamanoApr 8, 2011
  29. Jeff KingApr 8, 2011
  30. Jeff KingApr 8, 2011
  31. Alejandro R. SedeñoApr 22, 2011
  32. Jeff KingApr 22, 2011
  33. Alejandro R. SedeñoApr 22, 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.