From: Jakub Narebski <jnareb@gmail.com>
To: Sebastien Cevey <seb@cine7.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv3 1/3 (resend)] gitweb: Modularized git_get_project_description to be more generic
Date: Sun, 8 Feb 2009 12:10:48 +0100 [thread overview]
Message-ID: <200902081210.49328.jnareb@gmail.com> (raw)
In-Reply-To: <87zlgxp595.wl%seb@cine7.net>
Sebastien Cevey wrote:
[...]
> Sending this patch again. It has been rebased onto 621f1b so it should
> apply cleanly on the current git master branch.
Thanks a lot.
Due to changes to gitweb, while first patch in (earlier version of)
series applies cleanly, second patch didn't, and git could not find
base to fall back to 3-way merge (because second patch is based on
state after first patch, and situation after first patch changed).
It is much easier to rebase series if youhave them as commits, and
not as series of emails.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-02-08 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 23:24 [PATCHv3 1/3 (resend)] gitweb: Modularized git_get_project_description to be more generic Sebastien Cevey
2009-02-08 11:10 ` Jakub Narebski [this message]
[not found] ` <87tz75p3ej.wl%seb@cine7.net>
2009-02-08 12:34 ` Jakub Narebski
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=200902081210.49328.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=seb@cine7.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).