From: Junio C Hamano <junkio@cox.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Handle branch names with slashes
Date: Mon, 15 May 2006 23:48:04 -0700 [thread overview]
Message-ID: <7v64k6ea8r.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060516063541.GA11218@backpacker.hemma.treskal.com> (Karl Hasselström's message of "Tue, 16 May 2006 08:35:41 +0200")
Karl Hasselström <kha@treskal.com> writes:
> Teach stgit to handle branch names with slashes in them; that is,
> branches living in a subdirectory of .git/refs/heads.
>
> I had to change the patch@branch/top command-line syntax to
> patch@branch%top, in order to get sane parsing. The /top variant is
> still available for repositories that have no slashy branches; it is
> disabled as soon as there exists at least one subdirectory of
> refs/heads. Preferably, this compatibility hack can be killed some
> time in the future.
I wonder if using double-slashes is an easier alternative to
type than '%', like "patch@branch//top". That way, you do not
have to forbid per-cent sign in branch names.
next prev parent reply other threads:[~2006-05-16 6:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060510060040.GA3034@diana.vm.bytemark.co.uk>
2006-05-15 9:53 ` [PATCH 1/3] Don't die when there are no branches Karl Hasselström
2006-05-15 9:54 ` [PATCH 2/3] Handle branch names with slashes Karl Hasselström
2006-05-15 10:22 ` Catalin Marinas
2006-05-15 10:58 ` Karl Hasselström
2006-05-16 6:35 ` [PATCH 1/2] " Karl Hasselström
2006-05-16 6:48 ` Junio C Hamano [this message]
2006-05-16 7:45 ` Karl Hasselström
2006-05-17 15:18 ` Catalin Marinas
2006-05-18 6:42 ` Karl Hasselström
2006-05-18 6:50 ` [PATCH] " Karl Hasselström
2006-05-18 12:11 ` Catalin Marinas
2006-05-18 16:00 ` Karl Hasselström
2006-05-18 6:43 ` [PATCH 2/2] Tests for " Karl Hasselström
2006-05-16 6:37 ` Karl Hasselström
2006-05-15 9:55 ` [PATCH 3/3] " Karl Hasselström
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=7v64k6ea8r.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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