From: Petr Baudis <pasky@suse.cz>
To: Pavel Roskin <proski@gnu.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH 0/8] cogito: cg-object-id
Date: Wed, 21 Sep 2005 11:55:54 +0200 [thread overview]
Message-ID: <20050921095554.GD24902@pasky.or.cz> (raw)
In-Reply-To: <1127183518.31115.44.camel@dv>
Dear diary, on Tue, Sep 20, 2005 at 04:31:58AM CEST, I got a letter
where Pavel Roskin <proski@gnu.org> told me that...
> Hello!
Hello,
> These are the patches that implement cg-object-id and fix the bugs I
> found in process. The patches show separate stages of changes.
> Otherwise it would be a huge patch.
>
> This applies to all patches in the series
> Signed-off-by: Pavel Roskin <proski@gnu.org>
thanks, all but 6/8 applied. It'd make it easier for me if you included
the signed-off-by line in all the patches though, and it would make more
sense too.
Thanks,
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
prev parent reply other threads:[~2005-09-21 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 2:31 [PATCH 0/8] cogito: cg-object-id Pavel Roskin
2005-09-21 9:55 ` Petr Baudis [this message]
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=20050921095554.GD24902@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=proski@gnu.org \
/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).