From: Josh Triplett <josh@freedesktop.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ronald Landheer-Cieslak <ronald@landheer-cieslak.com>,
Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org
Subject: Re: [PATCH] Add support for # in URLs in git-remote (was: Re: [PATCH] New script: git-changelog.perl - revised)
Date: Tue, 13 Nov 2007 15:56:33 -0800 [thread overview]
Message-ID: <473A39B1.7050709@freedesktop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711031526060.4362@racer.site>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Johannes Schindelin wrote:
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-11-13 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 15:26 [PATCH] Add support for # in URLs in git-remote (was: Re: [PATCH] New script: git-changelog.perl - revised) Ronald Landheer-Cieslak
2007-11-03 15:27 ` Johannes Schindelin
2007-11-13 23:56 ` Josh Triplett [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473A39B1.7050709@freedesktop.org \
--to=josh@freedesktop.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ronald@landheer-cieslak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).