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

Re: [PATCH] Add support for # in URLs in git-remote (was: Re: [PATCH] New script: git-changelog.perl - revised)

From
Josh Triplett <josh@freedesktop.org>
Date
Nov 13, 2007, 23:56 UTC
Message-ID
<473A39B1.7050709@freedesktop.org>
In-Reply-To
<Pine.LNX.4.64.0711031526060.4362@racer.site>
Johannes Schindelin wrote:
Show 13 quoted lines
> On Sat, 3 Nov 2007, Ronald Landheer-Cieslak wrote:
>> The attached patch adds support for # signs in URLs passed to git-remote 
>> add.
> 
> NACK!
> 
> Please be polite enough to read up on the _many_ emails on this list about 
> this very subject.
> 
> Not doing so just _wastes_ our time.
> 
> Sorry for being so harsh, but this very subject easily cost me 20 hours in 
> total(!) in the last few weeks.

Perhaps this should go in the Git FAQ at http://git.or.cz/gitwiki/GitFaq . Does your message with Message-ID <Pine.LNX.4.64.0710162228560.25221@racer.site>, subject "Re: remote#branch", accurately describe the full problem with using #, namely that refs can contain #?

Any other problems besides not having the ability to reference more than one branch with this syntax?

- Josh Triplett
Previous: Johannes Schindelin
Message 3 of 3 in “Add support for # in URLs in git-remote (was: Re: [PATCH] New script: git-changelog.perl - revised)”
  1. Add support for # in URLs in git-remote (was: Re: [PATCH] New script: git-changelog.perl - revised)Ronald Landheer-Cieslak, Nov 3, 2007
  2. Johannes SchindelinNov 3, 2007
  3. Josh TriplettNov 13, 2007

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.