From: Junio C Hamano <junkio@cox•net>
To: "Dana How" <danahow@gmail•com>
Cc: "Git Mailing List" <git@vger•kernel.org>
Subject: Re: Rebase max-pack-size?
Date: Sat, 12 May 2007 15:57:31 -0700 [thread overview]
Message-ID: <7vmz09veec.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <56b7f5510705121325h65c62147h2b633fdddaece0be@mail.gmail.com> (Dana How's message of "Sat, 12 May 2007 13:25:30 -0700")
"Dana How" <danahow@gmail•com> writes:
> Since max-pack-size has appeared, and disappeard, in "pu" twice
> and never made it into "next", I'm guessing I should rebase/merge it on
> top of the other recent pack-objects work. I may get to this tonight;
> perhaps I'll send the patchset in one email with multiple attachments?
I am still holding onto the series on its own topic branch, but
merging it to 'pu' and resolving conflicts seem pointless while
I am (and hopefully the rest of the list ought to be ;-)
primarily concentrating on last-minute bugfixes in preparation
for v1.5.2.
A rebase to be queued in 'next' would be good, though.
Thanks.
next parent reply other threads:[~2007-05-12 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56b7f5510705121325h65c62147h2b633fdddaece0be@mail.gmail.com>
2007-05-12 22:57 ` Junio C Hamano [this message]
2007-05-14 15:47 Rebase max-pack-size? Dana How
2007-05-23 5:29 ` Junio C Hamano
2007-05-23 6:33 ` Dana How
2007-05-23 7:23 ` Junio C Hamano
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=7vmz09veec.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=danahow@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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