Re: [PATCH] fast-import: Stream very large blobs directly to pack
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Jan 29, 2010, 18:44 UTC
- Message-ID
- <20100129184403.GC22101@spearce.org>
- In-Reply-To
- <fabb9a1e1001291041w48776835m9b291923fbb859c3@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 9 quoted lines
> On Fri, Jan 29, 2010 at 19:37, Shawn O. Pearce <spearce@spearce.org> wrote: > > I was intentionally slating this for maint, to fix a bug a user > > reported when handling large streams. > > Ah, sorry, did not notice that. > > Speaking of which, how does one figure out what commit a patch > is/could be based on? Couldn't we include that in the part behind the > triple dash?
You have to tell the other guy in your cover letter section. You can try to guess if the index information is accurate by grepping around a log output looking for that blob sha-1 and then finding what branch that's in. Its not pretty.
IIRC other DVCS systems include the ancestor identity in their patch output. Git doesn't bother, because in a multi-patch series the 2nd (and subsequent) patches would have useless id information.
-- Shawn.