Re: stgit 0.13 import mbox problems
- From
- Catalin Marinas <catalin.marinas@gmail.com>
- Date
- Aug 23, 2007, 20:57 UTC
- Message-ID
- <b0943d9e0708231357s1ceaa121qd56e3a9c71677c8d@mail.gmail.com>
- In-Reply-To
- <20070823164322.GC5528@kroah.com>
On 23/08/07, Greg KH <greg@kroah.com> wrote:
> Also, it would import these patches, which are individually in mbox > form, with the incorrect author information. So I thought I would use > the mbox form to make sure I wasn't just doing something stupid.
If the patches have a "From: ..." line after the subject (as described in the submitting patches kernel docs), StGIT honours it.
Yet another way (might be even simpler for you) - use git-applymbox (or git-quiltapply) and 'stg uncommit -n 177'. The former generates GIT commits and the latter creates StGIT patches (without touching the tree, HEAD remains the same and corresponds to the top patch). There is also 'stg uncommit --to=commit-id'.
> > After an import failure, you can continue importing from the next > > patch using the 'stg import --ignore' option. > > Ok, will try that, and your patch.
You can try the tonight snapshot which has this patch included (and other fixes) - http://homepage.ntlworld.com/cmarinas/stgit/snapshots/stgit-20070823.tar.gz
Show 6 quoted lines
> > One thing you'll notice is the speed difference as stgit has to > > generate a git commit during a push operation. > > Oh yeah, I know that it would be slower, but I use git-quiltapply a lot > for sending patches to Linus, and that seems quite fast (actually a lot > faster than stgit for some reason...)
I should have a look at what git-quiltapply does as most of the StGIT waiting time on external GIT invocation.
Show 7 quoted lines
> $ stg series -d > + add-my-version-to-the-kernel | Add my version to the kernel. > + stupid-patch-for-my-laptop-whi | Stupid patch for my laptop which cant get sysrq-u > + gregs-test-driver-core-sysfs-s | Gregs test driver core / sysfs stress test module > > detect-atomic-counter-underflo | detect atomic counter underflows > > Are those spaces really the name of the patch?
No, the patch name is with the dashes, the rest is the patch subject line.
-- Catalin