git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Haberman <stephen@exigencecorp.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git/spearce.git (Oct 2008, #01; Mon, 06)
Date: Mon, 6 Oct 2008 15:48:49 -0500	[thread overview]
Message-ID: <20081006154849.6317f314.stephen@exigencecorp.com> (raw)
In-Reply-To: <20081006165943.GG8203@spearce.org>


> * sh/maint-rebase3 (Sun Oct 5 23:26:52 2008 -0500) 1 commit
>  - rebase--interactive: fix parent rewriting for dropped commits
> 
> A replacement for sh/maint-intrebase.  Its in pu because I have
> gotten 3 different versions of this patch, two of them posted a
> full 4 days after I merged the first version into next.  I felt
> burned by the patch author for not keeping up with my tree, so I'm
> not merging the patch to next.
>
> At this point its going to sit in pu until Junio comes back.
> I think the topic needs a few more days to settle to see if the
> patch author is going to submit any more revisions.

All fair enough.

Sorry for not keeping up with your tree--this was the first I heard my
first patch had made it into next, so I kept submitting new ones not
really knowing why they weren't generating feedback. My fault for not
actively looking into the pu/next thing--I'll know what to do next time.

Thanks,
Stephen

  reply	other threads:[~2008-10-06 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 16:59 What's cooking in git/spearce.git (Oct 2008, #01; Mon, 06) Shawn O. Pearce
2008-10-06 20:48 ` Stephen Haberman [this message]
2008-10-06 21:03 ` Jeff King
2008-10-07 14:50   ` Shawn O. Pearce

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=20081006154849.6317f314.stephen@exigencecorp.com \
    --to=stephen@exigencecorp.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).