From: Catalin Marinas <catalin.marinas@arm.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Sam Vilain <sam@vilain.net>, git@vger.kernel.org
Subject: Re: [PATCH] Handle branch names with slashes
Date: Mon, 27 Feb 2006 12:29:51 +0000 [thread overview]
Message-ID: <1141043391.3438.66.camel@pc1117> (raw)
In-Reply-To: <20060227121108.GA22398@diana.vm.bytemark.co.uk>
On Mon, 2006-02-27 at 13:11 +0100, Karl Hasselström wrote:
> There was a bug here after all: I just tried "stg pick
> multi@kha/patches" (to pick a patch named "multi" from the branch
> "kha/patches"), and StGIT tried to pick the patch from branch "kha".
I haven't applied your patch yet (too busy to properly review it).
> Looking closer, I realized that the complete patch specification
> syntax is "patchname@branchname/bottom", not
> "patchname/bottom@branchname" as I had assumed. This is obviously hard
> to reconcile with branch names containing /.
I don't have any strong opinion on either. Maybe we should use the
latter if it makes things easier for supporting branch names with /'s.
--
Catalin
next prev parent reply other threads:[~2006-02-27 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 17:35 bug: stgit doesn't handle branch names with / in them Karl Hasselström
2006-02-17 1:41 ` [PATCH] Handle branch names with slashes Karl Hasselström
2006-02-17 3:01 ` Sam Vilain
2006-02-17 4:21 ` Karl Hasselström
2006-02-27 12:11 ` Karl Hasselström
2006-02-27 12:29 ` Catalin Marinas [this message]
2006-02-27 13:09 ` Karl Hasselström
2006-02-17 9:47 ` Catalin Marinas
2006-02-17 9:53 ` Karl Hasselström
2006-04-12 19:16 ` Yann Dirson
2006-04-18 11:07 ` Karl Hasselström
-- strict thread matches above, loose matches on Subject: below --
2006-05-18 6:42 [PATCH 1/2] " 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
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=1141043391.3438.66.camel@pc1117 \
--to=catalin.marinas@arm.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=sam@vilain.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.