git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <greg@kroah.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Implement git-quiltimport (take 2)
Date: Fri, 19 May 2006 20:42:38 -0600	[thread overview]
Message-ID: <m1ac9dv2ld.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060519235825.GA3289@kroah.com> (Greg KH's message of "Fri, 19 May 2006 16:58:25 -0700")

Greg KH <greg@kroah.com> writes:

> On Thu, May 18, 2006 at 04:48:26AM -0600, Eric W. Biederman wrote:
>> 
>> Yes, a smaller patch series, that is what I meant.
>> Most quilt trees that I know about are  small.
>
> $ quilt series | wc -l
> 207
>
> And that is about "normal" for me.  Sometimes it grows to about 500+
> patches, but that only happens when there's a longer kernel release
> cycle.
>
> Another tree that I work on all the time is about 700+ patches, and yet
> another 2000+.  So you might re-evaluate your statement about "small"
> quilt series :)

Sure.  On fixing the upstream attribution issue you and Andi Kleen 
look like people that are worth talking to, as there were several
patches in Andrews tree from both of you that were lacking attribution.

> In looking at your script, it doesn't seem to be able to handle patches
> in quilt that are in mbox format.  Any thoughts to allow this to handle
> the attribution properly?

Mbox format but one patch per file, or multiple patches in one mbox file?

If it is one patch per file but with mbox headers, it is relatively
simple to teach git-mailinfo to parse things in a slightly more intelligent
way.  I played with that but I didn't have any patches that helped with.

> Right now my development flow has me converting my quilt tree to one big
> mbox file and then using 'git applymbox' to import it before asking
> Linus to pull from it.
>
> With your script I could skip at least one step, which would save me
> some time...

Sure. That is the point of making it generic.

Eric

  reply	other threads:[~2006-05-20  2:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 16:51 [PATCH] Implement git-quiltimport Eric W. Biederman
2006-05-16 17:03 ` Linus Torvalds
2006-05-16 17:53   ` Eric W. Biederman
2006-05-16 19:01     ` Junio C Hamano
2006-05-17  5:17       ` Eric W. Biederman
2006-05-17  5:31         ` Junio C Hamano
2006-05-17 18:44           ` [PATCH] Implement git-quiltimport (take 2) Eric W. Biederman
2006-05-17 18:51             ` Junio C Hamano
2006-05-17 19:20               ` Eric W. Biederman
2006-05-17 23:34                 ` Junio C Hamano
2006-05-18 10:48                   ` Eric W. Biederman
2006-05-19 23:58                     ` Greg KH
2006-05-20  2:42                       ` Eric W. Biederman [this message]
2006-05-20 21:32                         ` Greg KH
2006-05-21  0:36                           ` Eric W. Biederman
2006-05-21  0:41                             ` Junio C Hamano
2006-05-21  0:59                               ` Eric W. Biederman
2006-05-21  1:02                                 ` Junio C Hamano
2006-05-21  1:16                                   ` Eric W. Biederman
2006-06-01 19:23                             ` Greg KH
2006-06-02  0:24                               ` Eric W. Biederman
2006-05-19  9:55                   ` Eric W. Biederman
2006-05-17 20:10               ` [PATCH] Implement a --dry-run option to git-quiltimport Eric W. Biederman
2006-05-17 14:28         ` [PATCH] Implement git-quiltimport Linus Torvalds

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=m1ac9dv2ld.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=junkio@cox.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 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).