From: Jakub Narebski <jnareb@gmail.com>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: git@vger.kernel.org
Subject: Re: simple cvs-like git wrapper
Date: Fri, 1 Feb 2008 10:58:57 +0100 [thread overview]
Message-ID: <200802011058.59464.jnareb@gmail.com> (raw)
In-Reply-To: <20080201072935.GA941@informatik.uni-freiburg.de>
Uwe Kleine-König wrote:
>
> > Footonotes:
> > ===========
> > [*1*] I'd like to point to LKML post about creating perfect patch
> > *series*, but I have forgot to bookmark it, and canot find it again
> > (IIRC somebody posted link some time ago here on git mailing list).
>
> I remember:
>
> http://groups.google.com/group/linux.kernel/browse_thread/thread/26f1247fd4a2acbf/ac9743b603e53bae?lnk=gst&q=perfect+patch#ac9743b603e53bae
>
> . Do you mean that?
Thanks a lot, but it is not what I was searching for. This is interesting
article about what to put and what to not put in the cover letter [0/n],
while I am trying to find post about how to divide/split change into
series of commits implementing one separate part, so the whole is easy
to understand and bisectable.
--
Jakub Narebski
Poland
prev parent reply other threads:[~2008-02-01 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 20:40 simple cvs-like git wrapper Ed S. Peschko
2008-01-29 22:28 ` Jakub Narebski
2008-01-30 2:10 ` Ed S. Peschko
2008-01-30 4:00 ` Shawn O. Pearce
2008-01-30 22:52 ` Ed S. Peschko
2008-01-31 4:08 ` Shawn O. Pearce
2008-01-31 5:41 ` Ed S. Peschko
2008-01-31 6:01 ` Shawn O. Pearce
2008-01-31 6:17 ` Junio C Hamano
2008-01-30 19:49 ` Daniel Barkalow
2008-02-01 13:05 ` Kate Rhodes
2008-02-01 13:25 ` Johannes Schindelin
2008-02-01 15:35 ` Jakub Narebski
2008-02-01 7:29 ` Uwe Kleine-König
2008-02-01 9:58 ` Jakub Narebski [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=200802011058.59464.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=ukleinek@informatik.uni-freiburg.de \
/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).