From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] StGit patch series import
Date: Mon, 25 May 2009 00:04:31 +0200 [thread overview]
Message-ID: <cb7bb73a0905241504s7d531f0lb5908a499d4345f@mail.gmail.com> (raw)
In-Reply-To: <fabb9a1e0905241455j7045a920m11e7dcd6a92dd80a@mail.gmail.com>
On Sun, May 24, 2009 at 11:55 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> On Sun, May 24, 2009 at 23:43, Giuseppe Bilotta
> <giuseppe.bilotta@gmail.com> wrote:
>> As I mentioned, Wine uses plain git, and we've tried asking this
>> (non-core) developer to expose a standard git tree. But he finds StGIT
>> much more comfortable for the task.
>
> Silly question, doesn't StGit have an export option? Methinks if all
> the developer has to do is run 'stgit export' and then attach those
> patches instead of the raw patches, it'd be really lame of him not to
> do at least that?
That's what he does. The problem is that StGIT export exports a patch
series using a given template which (by default) is not in mailbox
format.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-05-24 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 7:19 [PATCH 0/2] StGit patch series import Giuseppe Bilotta
2009-05-24 20:49 ` Junio C Hamano
2009-05-24 21:43 ` Giuseppe Bilotta
2009-05-24 21:55 ` Sverre Rabbelier
2009-05-24 22:04 ` Giuseppe Bilotta [this message]
2009-05-24 22:05 ` Sverre Rabbelier
2009-05-24 22:02 ` Junio C Hamano
2009-05-24 22:18 ` Giuseppe Bilotta
2009-05-24 22:28 ` Sverre Rabbelier
2009-05-24 22:53 ` Giuseppe Bilotta
2009-05-24 22:57 ` Sverre Rabbelier
2009-05-24 23:03 ` Giuseppe Bilotta
2009-05-25 6:39 ` Junio C Hamano
2009-05-25 7:19 ` Giuseppe Bilotta
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=cb7bb73a0905241504s7d531f0lb5908a499d4345f@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@gmail.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).