Git development
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Handle branch names with slashes
Date: Fri, 17 Feb 2006 09:47:21 +0000	[thread overview]
Message-ID: <tnxbqx6z592.fsf@arm.com> (raw)
In-Reply-To: <20060217014117.12525.21330.stgit@backpacker.hemma.treskal.com> ( Karl Hasselström's message of "Fri, 17 Feb 2006 02:41:17 +0100")

Karl Hasselström <kha@treskal.com> wrote:
> Let StGIT grok branch names with slashes in them. It used to fall flat
> on its face when confronted with them.

Thanks for the patches you sent. I'll have a look at them tomorrow.

As a side note, for future patches, could you please use my
catalin.marinas@gmail.com address instead of the company one? I
maintain StGIT outside the working hours and it's much easier to grab
them from my personal address.

Thanks,

-- 
Catalin

  parent reply	other threads:[~2006-02-17  9:47 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
2006-02-27 13:09           ` Karl Hasselström
2006-02-17  9:47   ` Catalin Marinas [this message]
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=tnxbqx6z592.fsf@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=catalin.marinas@gmail.com \
    --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