All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: "Karl Hasselström" <kha@treskal.com>, git@vger.kernel.org
Subject: Re: [PATCH] Handle branch names with slashes
Date: Wed, 12 Apr 2006 21:16:55 +0200	[thread overview]
Message-ID: <20060412191655.GD27397@nowhere.earth> (raw)
In-Reply-To: <tnxbqx6z592.fsf@arm.com>

On Fri, Feb 17, 2006 at 09:47:21AM +0000, Catalin Marinas wrote:
> 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.

Is this still being worked on ?
-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>

  parent reply	other threads:[~2006-04-12 19:07 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
2006-02-17  9:53     ` Karl Hasselström
2006-04-12 19:16     ` Yann Dirson [this message]
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=20060412191655.GD27397@nowhere.earth \
    --to=ydirson@altern.org \
    --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 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.