From: Junio C Hamano <junkio@cox.net>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-fetch: Split fetch and merge logic
Date: Sat, 24 Feb 2007 02:23:15 -0800 [thread overview]
Message-ID: <7v8xenzwfg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <87ps7zj35b.fsf@gmail.com> (Santi Béjar's message of "Sat, 24 Feb 2007 10:50:08 +0100")
Santi Béjar <sbejar@gmail.com> writes:
> I've addressed all the comments, now prepared to even more comments :)
>
> Junio, from your "What's cooking in git.git (topics)" I undestand that
> the jc/fetch topic is not going to be in next soon (even for the first
> commit?). Anyway, the simple question is: Which branch (or commit) you
> want me to base this patch?
For now this is fine.
I might have to postpone rebasing jc/fetch on top of this one
depending on my workload, but I'd want this clean-up first.
Thanks.
next prev parent reply other threads:[~2007-02-24 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 9:50 [PATCH] git-fetch: Split fetch and merge logic Santi Béjar
2007-02-24 10:23 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-07 12:25 Santi Béjar
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=7v8xenzwfg.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sbejar@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