git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustav Hållberg" <gustav@gmail.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: "Karl Hasselström" <kha@treskal.com>, git@vger.kernel.org
Subject: Re: [StGit PATCH] Import git show output easily
Date: Wed, 2 Sep 2009 22:51:40 +0200	[thread overview]
Message-ID: <a1e915350909021351l315358a0s9d8c076440bc0fb7@mail.gmail.com> (raw)
In-Reply-To: <20090902175039.21633.25294.stgit@pc1117.cambridge.arm.com>

Somewhat related:

It would really rock if stg import could handle the regular patch "-p<N>" flag.
In particular, I miss -p0 as some broken versioning systems default to
such output.

- Gustav

  reply	other threads:[~2009-09-02 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 17:50 [StGit PATCH] Import git show output easily Catalin Marinas
2009-09-02 20:51 ` Gustav Hållberg [this message]
2009-09-02 20:54   ` Catalin Marinas

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=a1e915350909021351l315358a0s9d8c076440bc0fb7@mail.gmail.com \
    --to=gustav@gmail.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;
as well as URLs for NNTP newsgroup(s).