LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] jfs update
Date: Mon, 02 Oct 2006 10:41:15 -0500	[thread overview]
Message-ID: <1159803675.10207.15.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610020827390.3952@g5.osdl.org>

On Mon, 2006-10-02 at 08:31 -0700, Linus Torvalds wrote:
> 
> On Mon, 2 Oct 2006, Dave Kleikamp wrote:
> >
> >     Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
> >     (cherry picked from f74156539964d7b3d5164fdf8848e6a682f75b97 commit)
> 
> Btw, these cherry-pick messages are useless (and just noise) when sending 
> to me, since nobody will likely ever see the private tree that you 
> cherry-picked from, so the SHA1 won't ever match anything meaningful for 
> anybody but you.
> 
> So please either edit it out by hand ("git cherry-pick -e") or just ask 
> git to not generate it at all (the "-r" flag, for "replay"). I thought git 
> had already been fixed to not do this by default, but maybe I was 
> dreaming.

Okay.  This is the first time I used cherry-pick.  Since they were
generated by default, I left it alone.  I'll eliminate them in the
future.

I'm running git-1.4.2.2, which is pretty darn recent, so it doesn't look
like the default has been fixed.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2006-10-02 15:41 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 15:16 Dave Kleikamp
2006-10-02 15:31 ` Linus Torvalds
2006-10-02 15:41   ` Dave Kleikamp [this message]
2006-10-02 16:21     ` Al Viro
  -- strict thread matches above, loose matches on Subject: below --
2011-07-27 14:55 [GIT PULL] " Dave Kleikamp
2010-04-21 12:42 shaggy
2009-07-23 18:27 shaggy
2009-06-16 19:14 shaggy
2009-06-11 16:58 shaggy
2009-03-25 12:43 [git pull] " shaggy
2008-12-29 16:01 shaggy
2008-07-14 16:48 shaggy
2008-04-17 18:36 shaggy
2008-02-07 21:02 shaggy
2008-01-25 19:27 shaggy
2007-10-10 13:35 shaggy
2007-07-09 19:34 Dave Kleikamp
2007-05-08 14:51 Dave Kleikamp
2007-04-28 13:20 Dave Kleikamp
2007-02-14 23:08 Dave Kleikamp
2007-02-07 13:35 Dave Kleikamp
2006-12-12 15:16 Dave Kleikamp
2006-11-04  3:07 Dave Kleikamp
2006-11-02 14:23 Dave Kleikamp
2006-10-23 12:53 Dave Kleikamp
2006-09-25 13:04 Dave Kleikamp
2006-08-03 14:37 Dave Kleikamp
2006-07-14  1:45 Dave Kleikamp
2006-07-06 14:20 Dave Kleikamp
2006-05-24 13:10 Dave Kleikamp
2006-03-20 14:57 Dave Kleikamp
2006-03-14 18:47 Dave Kleikamp
2006-03-14 19:33 ` Linus Torvalds
2005-11-09 21:40 Dave Kleikamp
2005-10-28 19:12 Dave Kleikamp
2005-08-04 21:07 Dave Kleikamp
2005-07-27 18:05 Dave Kleikamp
2005-07-27 23:43 ` Linus Torvalds
2005-07-13 14:41 Dave Kleikamp
2005-06-20 16:18 Dave Kleikamp
2005-05-04 20:47 Dave Kleikamp
2005-05-04 21:37 ` Linus Torvalds
2005-05-05 18:16   ` Jeff Garzik
2005-05-05 18:22     ` Linus Torvalds
2005-05-05 18:51       ` Dave Kleikamp
2005-05-05 19:39         ` Andrew Morton
2005-05-06 19:13           ` Dave Kleikamp

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=1159803675.10207.15.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --subject='Re: [git pull] jfs update' \
    /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

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).