From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git/spearce.git (Sep 2008, #04; Mon, 22)
Date: Tue, 30 Sep 2008 13:00:52 +0200 [thread overview]
Message-ID: <81b0412b0809300400i164525ealce8a3ff8dabf783@mail.gmail.com> (raw)
In-Reply-To: <20080929184709.GB21310@spearce.org>
2008/9/29 Shawn O. Pearce <spearce@spearce.org>:
> Here are the topics that have been cooking. Commits prefixed
> with '-' are only in 'pu' while commits prefixed with '+' are
> in 'next'.
Would you mind adding the remove_path factorization patches
in there somewhere?
http://marc.info/?l=git&m=122246984212129&w=4
http://marc.info/?l=git&m=122246997012269&w=4
next prev parent reply other threads:[~2008-09-30 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:47 What's cooking in git/spearce.git (Sep 2008, #04; Mon, 22) Shawn O. Pearce
2008-09-30 7:52 ` Michael J Gruber
2008-09-30 18:36 ` Shawn O. Pearce
2008-09-30 11:00 ` Alex Riesen [this message]
2008-09-30 12:45 ` Alex Riesen
2008-09-30 18:28 ` 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=81b0412b0809300400i164525ealce8a3ff8dabf783@mail.gmail.com \
--to=raa.lkml@gmail.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).